From 60dd2c89ffb1f32b7d2d8c14a94cefb26c51aeca Mon Sep 17 00:00:00 2001
From: Slava Kim <slava@meteor.com>
Date: Mon, 30 Sep 2013 17:59:07 -0700
Subject: [PATCH] Clarify minimongo fields docs.

---
 docs/client/api.html | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/docs/client/api.html b/docs/client/api.html
index 9fa58c4fbbe..be68c131ef6 100644
--- a/docs/client/api.html
+++ b/docs/client/api.html
@@ -1261,12 +1261,13 @@ <h2 id="meteor_collection_cursor"><span>Cursors</span></h2>
     // Users.find({}, {fields: {password: 0, hash: 0}})
 
 To return an object that only includes the specified field, use `1` as
-the value.  The `_id` field is still included in the result.
+the value. The `_id` field is still included in the result.
 
     // Users.find({}, {fields: {firstname: 1, lastname: 1}})
 
-It is not possible to mix inclusion and exclusion styles (exception for `_id`).
-Field operators such as `$` and `$elemMatch` are not available on client side yet.
+It is not possible to mix inclusion and exclusion styles (except for the cases
+when `_id` is included by default or explicitly included). Field operators such
+as `$` and `$elemMatch` are not available on the client side yet.
 
 More advanced example:
 
@@ -1278,7 +1279,8 @@ <h2 id="meteor_collection_cursor"><span>Cursors</span></h2>
 
     // returns { alterEgos: [{ name: "Kira" }, { name: "L" }] }
 
-Notice the nested field rule and array behavior, learn more in MongoDB docs.
+See <a href="http://docs.mongodb.org/manual/tutorial/project-fields-from-query-results/#projection">
+the MongoDB docs</a> for details of the nested field rules and array behavior.
 
 {{/api_box_inline}}