From b59866c0de381592bedd7f86b80dff1e2c366456 Mon Sep 17 00:00:00 2001 From: Abdulrazak Alahmad Date: Thu, 8 Sep 2022 18:48:26 +0200 Subject: [PATCH] fix_misspelling_pipeline --- exercises/03_advanced-mongo-queries.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exercises/03_advanced-mongo-queries.md b/exercises/03_advanced-mongo-queries.md index 2423b0f..df4459d 100644 --- a/exercises/03_advanced-mongo-queries.md +++ b/exercises/03_advanced-mongo-queries.md @@ -43,7 +43,7 @@ db.cricket_players.aggregate([ { "_id" : "Right_Hand", "playerCountByBattingHand" : 345 } ``` -:arrow_right: A word on the aggregate pipleine syntax: By now, we're all familiar with the JSON format of **key: value** pairs. +:arrow_right: A word on the aggregate pipeline syntax: By now, we're all familiar with the JSON format of **key: value** pairs. - Whenever a field is accessed as the **key**, it is written as it is. We've seen numerous examples of this starting from our very first filtering query `db.movieDetails.count({"rated": "PG-13"})`. - Here the field `rated` is used as a key and is simply written as `rated`.