Skip to content

Correct spelling & grammar in 4.4 doctrine/ #16271

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 14, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion doctrine/associations.rst
Original file line number Diff line number Diff line change
Expand Up @@ -299,7 +299,7 @@ config.
*exactly* like an array, but has some added flexibility. Just imagine that
it is an ``array`` and you'll be in good shape.

Your database is setup! Now, run the migrations like normal:
Your database is set up! Now, run the migrations like normal:

.. code-block:: terminal

Expand Down
2 changes: 1 addition & 1 deletion doctrine/dbal.rst
Original file line number Diff line number Diff line change
Expand Up @@ -120,7 +120,7 @@ Registering custom Mapping Types in the SchemaTool

The SchemaTool is used to inspect the database to compare the schema. To
achieve this task, it needs to know which mapping type needs to be used
for each database types. Registering new ones can be done through the configuration.
for each database type. Registering new ones can be done through the configuration.

Now, map the ENUM type (not supported by DBAL by default) to the ``string``
mapping type:
Expand Down
4 changes: 2 additions & 2 deletions doctrine/registration_form.rst
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ form you must:
#. :doc:`Create a form </forms>` to ask for the registration information (you can
generate this with the ``make:registration-form`` command provided by the `MakerBundle`_);
#. Create :doc:`a controller </controller>` to :ref:`process the form <processing-forms>`;
#. :ref:`Protect some parts of your application <security-authorization>` so
only registered users can access to them.
#. :ref:`Protect some parts of your application <security-authorization>` so that
only registered users can access them.

.. _`MakerBundle`: https://symfony.com/doc/current/bundles/SymfonyMakerBundle/index.html
2 changes: 1 addition & 1 deletion doctrine/resolve_target_entity.rst
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
How to Define Relationships with Abstract Classes and Interfaces
================================================================

One of the goals of bundles is to create discreet bundles of functionality
One of the goals of bundles is to create discrete bundles of functionality
that do not have many (if any) dependencies, allowing you to use that
functionality in other applications without including unnecessary items.

Expand Down
4 changes: 2 additions & 2 deletions doctrine/reverse_engineering.rst
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ How to Generate Entities from an Existing Database
==================================================

When starting work on a brand new project that uses a database, two different
situations comes naturally. In most cases, the database model is designed
situations can occur. In most cases, the database model is designed
and built from scratch. Sometimes, however, you'll start with an existing and
probably unchangeable database model. Fortunately, Doctrine comes with a bunch
of tools to help generate model classes from your existing database.
Expand Down Expand Up @@ -47,7 +47,7 @@ to a post record thanks to a foreign key constraint.
) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

Before diving into the recipe, be sure your database connection parameters are
correctly setup in the ``.env`` file (or ``.env.local`` override file).
correctly set up in the ``.env`` file (or ``.env.local`` override file).

The first step towards building entity classes from an existing database
is to ask Doctrine to introspect the database and generate the corresponding
Expand Down