Merge pull request #20 from Meg528/patch-12

Update 6-writing-long-pipelines.mdx

Author: dfreniche

docs/30-simple-queries/6-writing-long-pipelines.mdx

@@ -1,14 +1,14 @@
-# 👐 Writing long pipelines
+# 👐 Writing Long Pipelines
 
-Aggregation pipelines can get very long, depending on how many stages we need to run. Writing a pipeline is writing code, as you will write it using one of the many MongoDB drivers in your own language. Here we're presenting the examples using JavaScript suitable for the MongoDB Shell [mongosh](https://www.mongodb.com/docs/mongodb-shell/), but if you are writing a microservice in Rust, you'll definitely write your pipelines in Rust.
+Aggregation pipelines can get very long, depending on how many stages we need to run. Writing a pipeline is writing code, as you will write it using one of the many MongoDB drivers in your own language. Here we're presenting the examples using JavaScript suitable for the MongoDB shell [mongosh](https://www.mongodb.com/docs/mongodb-shell/), but if you are writing a microservice in Rust, you'll definitely write your pipelines in Rust.
 
 :::danger
 The following syntax doesn't work in the Atlas UI aggregations editor. The editor doesn't support declaring variables.
 :::
 
 This is why we should rewrite our last pipeline like this:
 
-Get 15 books from 1985 with 150 pages. Show only the `title`, `year`, `totalInventory` and `available` books. (Sample doc [here](/docs/simple-queries/project))
+Get 15 books from 1985 with 150 pages. Show only the `title`, `year`, `totalInventory`, and `available` books (sample doc [here](/docs/simple-queries/project)).
 
 ```js
 db.books.aggregate([
@@ -30,26 +30,26 @@ db.books.aggregate([
 ]);
 ```
 
-Easier to read, and reason about, right?
+Easier to read and understand, right?
 
-👐 Try to run the above pipeline and compare your results: should be the same as before
+👐 Try to run the above pipeline and compare your results. They should be the same as before.
 
 :::tip
 
-Write your aggregation pipelines like you'll compose functions in your programming language. Aggregations _are_ code that runs on the server. In the client you just express _what_ you want to be done, not _how_ to do it.
+Write your aggregation pipelines like you'll compose functions in your programming language. Aggregations _are_ code that runs on the server. In the client, you just express _what_ you want to be done, not _how_ to do it.
 
 :::
 
 :::tip
 
-As this is code, we can even add comments (starting with `//`) to our pipelines
+As this is code, we can even add comments (starting with `//`) to our pipelines.
 
 :::
 
 
-👐 We can also use $gte to get the books with 150 pages or more. Check $gte syntax in the [docucumentation](https://www.mongodb.com/docs/manual/reference/operator/query/gte/) and write an aggregation pipeline to return 15 books from 1985 with more than 150 pages. Show only the `title`, `year`, `totalInventory` and `available` books. (Sample doc [here](/docs/simple-queries/project))
+👐 We can also use $gte to get the books with 150 pages or more. Check $gte syntax in the [docucumentation](https://www.mongodb.com/docs/manual/reference/operator/query/gte/) and write an aggregation pipeline to return 15 books from 1985 with more than 150 pages. Show only the `title`, `year`, `totalInventory`, and `available` books (sample doc [here](/docs/simple-queries/project)).
 
-_Hint:_ we'll need to use `$and` as maybe this is a bit more complex.
+_Hint:_ We'll need to use `$and` as maybe this is a bit more complex.
 
 <details>
 <summary>Answer</summary>