diff --git a/docs/populate.md b/docs/populate.md
index adc6e8a6d59..9026f140fe4 100644
--- a/docs/populate.md
+++ b/docs/populate.md
@@ -44,12 +44,13 @@ user and have a good reason for doing so.
Field Selection
Populating Multiple Paths
Query conditions and other options
+ limit
vs. perDocumentLimit
Refs to children
Populating an existing document
Populating multiple existing documents
Populating across multiple levels
Populating across Databases
- Dynamic References via `refPath`
+ Dynamic References via refPath
Populate Virtuals
Populate Virtuals: The Count Option
Populate Virtuals: The Match Option
@@ -275,7 +276,7 @@ story; // null
If you want to filter stories by their author's name, you should use [denormalization](https://www.mongodb.com/blog/post/6-rules-of-thumb-for-mongodb-schema-design-part-3).
-
+
Populate does support a `limit` option, however, it currently
does **not** limit on a per-document basis for backwards compatibility. For example,
@@ -485,9 +486,8 @@ const events = await Event.
populate({ path: 'conversation', model: Conversation });
```
-
-
-Mongoose can also populate from multiple collections based on the value
+
+
of a property in the document. Let's say you're building a schema for
storing comments. A user may comment on either a blog post or a product.