@@ -171,17 +171,22 @@ $rename
171
171
Before version 2.2, when renaming multiple fields and only some (but
172
172
not all) old field names refer to non-existing fields:
173
173
174
- - **if** no field exists with the new field name, the
175
- :operator:`$rename` operator does nothing.
174
+ - For the fields with the old names that do exist, the
175
+ :operator:`$rename` operator renames these fields to the
176
+ specified new field names.
177
+
178
+ - For the fields with the old names that do **not** exist:
179
+
180
+ - **if** no field exists with the new field name, the
181
+ :operator:`$rename` operator does nothing.
176
182
177
- - **if** fields already exist with the new field names, the
178
- :operator:`$rename` operator drops these fields.
183
+ - **if** fields already exist with the new field names, the
184
+ :operator:`$rename` operator drops these fields.
179
185
180
- Consider the following operation that renames both the
181
- field ``mobile``, which exists, the field ``wife``, which
182
- does not exist. The operation will set the
183
- field named ``wife`` ``alias``, which is the name of an
184
- existing field:
186
+ Consider the following operation that renames both the field
187
+ ``mobile``, which exists, and the field ``wife``, which does
188
+ not exist. The operation tries to set the field named ``wife``
189
+ to ``alias``, which is the name of an existing field:
185
190
186
191
.. code-block:: javascript
187
192
0 commit comments