Skip to content
This repository was archived by the owner on Apr 2, 2018. It is now read-only.

Commit 20bcbc8

Browse files
committed
Merge pull request #9 from marnusw/spelling_mistakes
Fixed two spelling mistakes in the introduction.
2 parents 3e272b5 + a5d7c1c commit 20bcbc8

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

en/reference/configuration.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ Bootstrapping
55
-------------
66

77
Bootstrapping Doctrine is a relatively simple procedure that
8-
roughly exists of just 2 steps:
8+
roughly consists of just 2 steps:
99

1010

1111
- Making sure Doctrine class files can be loaded on demand.
@@ -21,7 +21,7 @@ Doctrine CouchDB has dependencies on two other libraries:
2121

2222
You have to make sure that both dependencies are installed and autoloadable.
2323

24-
The Github checkout of comes with a submodule of the Doctrine Common library. It contains
24+
The Github checkout comes with a submodule of the Doctrine Common library. It contains
2525
the ``Doctrine\Common\ClassLoader`` which should be used for autoloading all the necessary
2626
Doctrine classes.
2727

en/reference/introduction.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ Features
2121
Architecture
2222
------------
2323

24-
The Doctrine persistence semantics demand a strict separation of persistence and business logic. This means the PHP Objects that you can map to CouchDB documents do not extend any base class or implement any interface. These objects and their associations between each other don't even know that they are saved inside the CouchDB, fow all they know it could also be the ORM or MongoDB solving their persistence needs. Instead of having ``save()``, ``delete()`` and finder methods on your PHP objects Doctrine CouchDB ODM provides you with a management/query layer that translates between CouchDB documents and PHP objects.
24+
The Doctrine persistence semantics demand a strict separation of persistence and business logic. This means the PHP Objects that you can map to CouchDB documents do not extend any base class or implement any interface. These objects and their associations between each other don't even know that they are saved inside the CouchDB, for all they know it could also be the ORM or MongoDB solving their persistence needs. Instead of having ``save()``, ``delete()`` and finder methods on your PHP objects Doctrine CouchDB ODM provides you with a management/query layer that translates between CouchDB documents and PHP objects.
2525

2626
For example take this BlogPost entity:
2727

@@ -86,7 +86,7 @@ No abstract/base-class nor interface was implemented, yet you can save an object
8686
text: { type: string }
8787
publishDate: { type: datetime }
8888
89-
This simple definitions describe to Doctrine CouchDB ODM what parts of your object should be mapped. Now your application code saving an instance of a blog post will look like the following lines:
89+
These simple definitions describe to Doctrine CouchDB ODM what parts of your object should be mapped. Now your application code saving an instance of a blog post will look like the following lines:
9090

9191
.. code-block:: php
9292

0 commit comments

Comments
 (0)