Skip to content

Commit 6b38408

Browse files
committed
MW PR fixes 2
1 parent 772600e commit 6b38408

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

source/add-existing.txt

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ application that uses {+odm+}, see one of the following guides:
3030
Sinatra Application
3131
-------------------
3232

33-
To start using {+odm+} in an existing Sinatra application, you can follow
33+
To start using {+odm+} in an existing Sinatra application, perform
3434
the following steps:
3535

3636
1. Add the ``mongoid`` dependency to your application's ``Gemfile``.
@@ -103,7 +103,7 @@ Modify Frameworks
103103
Open the ``config/application.rb`` file and examine the contents. If the
104104
file uses the ``require "rails/all"`` statement to load all Rails components,
105105
delete this statement. You must add a separate ``require`` statement
106-
for each Rails component, as shown the following sample
106+
for each Rails component, as shown in the following sample
107107
``config/application.rb`` file:
108108

109109
.. code-block:: ruby
@@ -206,8 +206,8 @@ a predefined schema to store the data.
206206

207207
Migration tools are often specific to datasets.
208208
Even though {+odm+} supports a superset of Active Record associations,
209-
the way that model references are stored in collections is different between
210-
{+odm+} and Active Record.
209+
model references are stored differently in collections when using
210+
{+odm+} compared to Active Record.
211211

212212
Visit the following resources to learn more about migrating from an
213213
RDBMS to MongoDB:

0 commit comments

Comments
 (0)