Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

Commit f285d93

Browse filesBrowse files
weaverryanweaverryan
committed
minor #3451 some language tweaks (AE, third-person perspective) (xabbuh)
This PR was merged into the 2.3 branch. Discussion ---------- some language tweaks (AE, third-person perspective) | Q | A | ------------- | --- | Doc fix? | yes | New docs? | no | Applies to | all | Fixed tickets | Commits ------- 0aad5d3 some language tweaks (AE, third-person perspective)
2 parents 2b7e0f6 + 0aad5d3 commit f285d93
Copy full SHA for f285d93
Expand file treeCollapse file tree

32 files changed

+70
-73
lines changed

‎book/forms.rst

Copy file name to clipboardExpand all lines: book/forms.rst
+3-3Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -281,7 +281,7 @@ Submitting Forms with Multiple Buttons
281281

282282
When your form contains more than one submit button, you will want to check
283283
which of the buttons was clicked to adapt the program flow in your controller.
284-
Let's add a second button with the caption "Save and add" to our form::
284+
To do this, add a second button with the caption "Save and add" to your form::
285285

286286
$form = $this->createFormBuilder($task)
287287
->add('task', 'text')
@@ -552,8 +552,8 @@ Groups based on the Clicked Button
552552
When your form contains multiple submit buttons, you can change the validation
553553
group depending on which button is used to submit the form. For example,
554554
consider a form in a wizard that lets you advance to the next step or go back
555-
to the previous step. Let's assume also that when returning to the previous
556-
step, the data of the form should be saved, but not validated.
555+
to the previous step. Also assume that when returning to the previous step,
556+
the data of the form should be saved, but not validated.
557557

558558
First, we need to add the two buttons to the form::
559559

‎book/from_flat_php_to_symfony2.rst

Copy file name to clipboardExpand all lines: book/from_flat_php_to_symfony2.rst
+2-4Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -75,8 +75,6 @@ to maintain. There are several problems that need to be addressed:
7575
tied to MySQL. Though not covered here, Symfony2 fully integrates `Doctrine`_,
7676
a library dedicated to database abstraction and mapping.
7777

78-
Let's get to work on solving these problems and more.
79-
8078
Isolating the Presentation
8179
~~~~~~~~~~~~~~~~~~~~~~~~~~
8280

@@ -673,8 +671,8 @@ Where Symfony2 Delivers
673671
~~~~~~~~~~~~~~~~~~~~~~~
674672

675673
In the upcoming chapters, you'll learn more about how each piece of Symfony
676-
works and the recommended organization of a project. For now, let's see how
677-
migrating the blog from flat PHP to Symfony2 has improved life:
674+
works and the recommended organization of a project. For now, have a look
675+
at how migrating the blog from flat PHP to Symfony2 has improved life:
678676

679677
* Your application now has **clear and consistently organized code** (though
680678
Symfony doesn't force you into this). This promotes **reusability** and

‎book/security.rst

Copy file name to clipboardExpand all lines: book/security.rst
+3-3Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -148,8 +148,8 @@ that looks like the following:
148148
* All URLs *not* matching ``/admin/*`` are accessible by all users (and the
149149
user is never prompted to log in).
150150

151-
Let's look briefly at how security works and how each part of the configuration
152-
comes into play.
151+
Read this short summary about how security works and how each part of the
152+
configuration comes into play.
153153

154154
How Security Works: Authentication and Authorization
155155
----------------------------------------------------
@@ -541,7 +541,7 @@ And that's it! When you submit the form, the security system will automatically
541541
check the user's credentials and either authenticate the user or send the
542542
user back to the login form where the error can be displayed.
543543

544-
Let's review the whole process:
544+
To review the whole process:
545545

546546
#. The user tries to access a resource that is protected;
547547
#. The firewall initiates the authentication process by redirecting the

‎components/console/introduction.rst

Copy file name to clipboardExpand all lines: components/console/introduction.rst
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ You can install the component in 2 different ways:
2727
configured with an ANSI driver and your console commands invoke other scripts which
2828
emit ANSI color sequences, they will be shown as raw escape characters.
2929

30-
To enable ANSI colour support for Windows, please install `ANSICON`_.
30+
To enable ANSI color support for Windows, please install `ANSICON`_.
3131

3232
Creating a basic Command
3333
------------------------

‎components/filesystem.rst

Copy file name to clipboardExpand all lines: components/filesystem.rst
+2-2Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -162,8 +162,8 @@ the mode of a file. The fourth argument is a boolean recursive option::
162162
Remove
163163
~~~~~~
164164

165-
:method:`Symfony\\Component\\Filesystem\\Filesystem::remove` let's you remove
166-
files, symlink, directories easily::
165+
:method:`Symfony\\Component\\Filesystem\\Filesystem::remove` is used to remove
166+
files, symlinks, directories easily::
167167

168168
$fs->remove(array('symlink', '/path/to/directory', 'activity.log'));
169169

‎components/http_foundation/session_configuration.rst

Copy file name to clipboardExpand all lines: components/http_foundation/session_configuration.rst
+2-2Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ Configuring Sessions and Save Handlers
77

88
This section deals with how to configure session management and fine tune it
99
to your specific needs. This documentation covers save handlers, which
10-
store and retrieve session data, and configuring session behaviour.
10+
store and retrieve session data, and configuring session behavior.
1111

1212
Save Handlers
1313
~~~~~~~~~~~~~
@@ -57,7 +57,7 @@ Example usage::
5757

5858
Native save handlers provide a quick solution to session storage, however, in complex systems
5959
where you need more control, custom save handlers may provide more freedom and flexibility.
60-
Symfony2 provides several implementations which you may further customise as required.
60+
Symfony2 provides several implementations which you may further customize as required.
6161

6262
Custom Save Handlers
6363
--------------------

‎components/routing/introduction.rst

Copy file name to clipboardExpand all lines: components/routing/introduction.rst
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ In order to set up a basic routing system you need three parts:
2525
* A :class:`Symfony\\Component\\Routing\\RequestContext`, which has information about the request
2626
* A :class:`Symfony\\Component\\Routing\\Matcher\\UrlMatcher`, which performs the mapping of the request to a single route
2727

28-
Let's see a quick example. Notice that this assumes that you've already configured
28+
Here is a quick example. Notice that this assumes that you've already configured
2929
your autoloader to load the Routing component::
3030

3131
use Symfony\Component\Routing\Matcher\UrlMatcher;

‎components/serializer.rst

Copy file name to clipboardExpand all lines: components/serializer.rst
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -129,7 +129,7 @@ method on the normalizer definition::
129129
Deserializing an Object
130130
-----------------------
131131

132-
Let's see now how to do the exactly the opposite. This time, the information
132+
You'll now learn how to do the exact opposite. This time, the information
133133
of the ``Person`` class would be encoded in XML format::
134134

135135
$data = <<<EOF

‎cookbook/assetic/apply_to_option.rst

Copy file name to clipboardExpand all lines: cookbook/assetic/apply_to_option.rst
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ How to Apply an Assetic Filter to a Specific File Extension
66

77
Assetic filters can be applied to individual files, groups of files or even,
88
as you'll see here, files that have a specific extension. To show you how
9-
to handle each option, let's suppose that you want to use Assetic's CoffeeScript
9+
to handle each option, suppose that you want to use Assetic's CoffeeScript
1010
filter, which compiles CoffeeScript files into JavaScript.
1111

1212
The main configuration is just the paths to coffee, node and node_modules.

‎cookbook/cache/varnish.rst

Copy file name to clipboardExpand all lines: cookbook/cache/varnish.rst
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -90,7 +90,7 @@ that will invalidate the cache for a given resource:
9090
9191
sub vcl_recv {
9292
/*
93-
Varnish default behaviour doesn't support PURGE.
93+
Varnish default behavior doesn't support PURGE.
9494
Match the PURGE request and immediately do a cache lookup,
9595
otherwise Varnish will directly pipe the request to the backend
9696
and bypass the cache

‎cookbook/configuration/apache_router.rst

Copy file name to clipboardExpand all lines: cookbook/configuration/apache_router.rst
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ Symfony2 to use the ``ApacheUrlMatcher`` instead of the default one:
5252
Generating mod_rewrite rules
5353
----------------------------
5454

55-
To test that it's working, let's create a very basic route for the AcmeDemoBundle:
55+
To test that it's working, create a very basic route for the AcmeDemoBundle:
5656

5757
.. configuration-block::
5858

‎cookbook/configuration/override_dir_structure.rst

Copy file name to clipboardExpand all lines: cookbook/configuration/override_dir_structure.rst
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ the location of the cache directory to ``app/{environment}/cache``.
5151
.. caution::
5252

5353
You should keep the ``cache`` directory different for each environment,
54-
otherwise some unexpected behaviour may happen. Each environment generates
54+
otherwise some unexpected behavior may happen. Each environment generates
5555
its own cached config files, and so each needs its own directory to store
5656
those cache files.
5757

‎cookbook/deployment-tools.rst

Copy file name to clipboardExpand all lines: cookbook/deployment-tools.rst
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ How to deploy a Symfony2 application
3434

3535
There are several ways you can deploy a Symfony2 application.
3636

37-
Let's start with a few basic deployment strategies and build up from there.
37+
Start with a few basic deployment strategies and build up from there.
3838

3939
Basic File Transfer
4040
~~~~~~~~~~~~~~~~~~~

‎cookbook/doctrine/dbal.rst

Copy file name to clipboardExpand all lines: cookbook/doctrine/dbal.rst
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -131,7 +131,7 @@ The SchemaTool is used to inspect the database to compare the schema. To
131131
achieve this task, it needs to know which mapping type needs to be used
132132
for each database types. Registering new ones can be done through the configuration.
133133

134-
Let's map the ENUM type (not supported by DBAL by default) to a the ``string``
134+
Now, map the ENUM type (not supported by DBAL by default) to the ``string``
135135
mapping type:
136136

137137
.. configuration-block::

‎cookbook/doctrine/resolve_target_entity.rst

Copy file name to clipboardExpand all lines: cookbook/doctrine/resolve_target_entity.rst
+3-3Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -34,8 +34,8 @@ with a real object that implements that interface.
3434
Set up
3535
------
3636

37-
Let's use the following basic entities (which are incomplete for brevity)
38-
to explain how to set up and use the RTEL.
37+
This article uses the following two basic entities (which are incomplete for
38+
brevity) to explain how to set up and use the ``ResolveTargetEntityListener``.
3939

4040
A Customer entity::
4141

@@ -53,7 +53,7 @@ A Customer entity::
5353
*/
5454
class Customer extends BaseCustomer implements InvoiceSubjectInterface
5555
{
56-
// In our example, any methods defined in the InvoiceSubjectInterface
56+
// In this example, any methods defined in the InvoiceSubjectInterface
5757
// are already implemented in the BaseCustomer
5858
}
5959

‎cookbook/form/create_custom_field_type.rst

Copy file name to clipboardExpand all lines: cookbook/form/create_custom_field_type.rst
+4-4Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -99,10 +99,10 @@ part by the value of your ``getName()`` method. For more information, see
9999

100100
In this case, since the parent field is ``choice``, you don't *need* to do
101101
any work as the custom field type will automatically be rendered like a ``choice``
102-
type. But for the sake of this example, let's suppose that when your field
103-
is "expanded" (i.e. radio buttons or checkboxes, instead of a select field),
104-
you want to always render it in a ``ul`` element. In your form theme template
105-
(see above link for details), create a ``gender_widget`` block to handle this:
102+
type. But for the sake of this example, suppose that when your field is "expanded"
103+
(i.e. radio buttons or checkboxes, instead of a select field), you want to
104+
always render it in a ``ul`` element. In your form theme template (see above
105+
link for details), create a ``gender_widget`` block to handle this:
106106

107107
.. configuration-block::
108108

‎cookbook/form/create_form_type_extension.rst

Copy file name to clipboardExpand all lines: cookbook/form/create_form_type_extension.rst
+5-5Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -39,9 +39,9 @@ template. But field type extensions allow you to do this in a nice DRY fashion.
3939
Defining the Form Type Extension
4040
--------------------------------
4141

42-
Your first task will be to create the form type extension class. Let's
43-
call it ``ImageTypeExtension``. By standard, form extensions usually live
44-
in the ``Form\Extension`` directory of one of your bundles.
42+
Your first task will be to create the form type extension class (called ``ImageTypeExtension``
43+
in this article). By standard, form extensions usually live in the ``Form\Extension``
44+
directory of one of your bundles.
4545

4646
When creating a form type extension, you can either implement the
4747
:class:`Symfony\\Component\\Form\\FormTypeExtensionInterface` interface
@@ -133,8 +133,8 @@ Adding the extension Business Logic
133133
-----------------------------------
134134

135135
The goal of your extension is to display nice images next to file inputs
136-
(when the underlying model contains images). For that purpose, let's assume
137-
that you use an approach similar to the one described in
136+
(when the underlying model contains images). For that purpose, suppose that
137+
you use an approach similar to the one described in
138138
:doc:`How to handle File Uploads with Doctrine </cookbook/doctrine/file_uploads>`:
139139
you have a Media model with a file property (corresponding to the file field
140140
in the form) and a path property (corresponding to the image path in the

‎cookbook/form/dynamic_form_modification.rst

Copy file name to clipboardExpand all lines: cookbook/form/dynamic_form_modification.rst
+3-3Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -29,8 +29,8 @@ field.
2929
Customizing your Form based on the underlying Data
3030
--------------------------------------------------
3131

32-
Before jumping right into dynamic form generation, let's have a quick review
33-
of what a bare form class looks like::
32+
Before jumping right into dynamic form generation, hold on and recall what
33+
a bare form class looks like::
3434

3535
// src/Acme/DemoBundle/Form/Type/ProductType.php
3636
namespace Acme\DemoBundle\Form\Type;
@@ -226,7 +226,7 @@ How to Dynamically Generate Forms based on user Data
226226

227227
Sometimes you want a form to be generated dynamically based not only on data
228228
from the form but also on something else - like some data from the current user.
229-
Suppose you have a social website where a user can only message people marked
229+
Suppose you have a social website where a user can only message people marked
230230
as friends on the website. In this case, a "choice list" of whom to message
231231
should only contain users that are the current user's friends.
232232

‎cookbook/form/form_collections.rst

Copy file name to clipboardExpand all lines: cookbook/form/form_collections.rst
+3-4Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -20,8 +20,8 @@ that Task, right inside the same form.
2020
including the ``ManyToMany`` association mapping definition on the Task's
2121
``tags`` property.
2222

23-
Let's start there: suppose that each ``Task`` belongs to multiple ``Tag``
24-
objects. Start by creating a simple ``Task`` class::
23+
First, suppose that each ``Task`` belongs to multiple ``Tag`` objects. Start
24+
by creating a simple ``Task`` class::
2525

2626
// src/Acme/TaskBundle/Entity/Task.php
2727
namespace Acme\TaskBundle\Entity;
@@ -77,8 +77,7 @@ objects::
7777
The ``name`` property is public here, but it can just as easily be protected
7878
or private (but then it would need ``getName`` and ``setName`` methods).
7979

80-
Now let's get to the forms. Create a form class so that a ``Tag`` object
81-
can be modified by the user::
80+
Then, create a form class so that a ``Tag`` object can be modified by the user::
8281

8382
// src/Acme/TaskBundle/Form/Type/TagType.php
8483
namespace Acme\TaskBundle\Form\Type;

‎cookbook/form/inherit_data_option.rst

Copy file name to clipboardExpand all lines: cookbook/form/inherit_data_option.rst
+4-4Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ entities, a ``Company`` and a ``Customer``::
4444
As you can see, each entity shares a few of the same fields: ``address``,
4545
``zipcode``, ``city``, ``country``.
4646

47-
Let's build two forms for these entities, ``CompanyType`` and ``CustomerType``::
47+
Start with building two forms for these entities, ``CompanyType`` and ``CustomerType``::
4848

4949
// src/Acme/HelloBundle/Form/Type/CompanyType.php
5050
namespace Acme\HelloBundle\Form\Type;
@@ -81,8 +81,8 @@ Let's build two forms for these entities, ``CompanyType`` and ``CustomerType``::
8181
}
8282
8383
Instead of including the duplicated fields ``address``, ``zipcode``, ``city``
84-
and ``country`` in both of these forms, we will create a third form for that.
85-
We will call this form simply ``LocationType``::
84+
and ``country`` in both of these forms, create a third form called ``LocationType``
85+
for that::
8686

8787
// src/Acme/HelloBundle/Form/Type/LocationType.php
8888
namespace Acme\HelloBundle\Form\Type;
@@ -127,7 +127,7 @@ access the properties of the ``Customer`` instance instead. Easy, eh?
127127
can also (just like with any option) pass it in the third argument of
128128
``$builder->add()``.
129129

130-
Let's make this work by adding the location form to our two original forms::
130+
Finally, make this work by adding the location form to your two original forms::
131131

132132
// src/Acme/HelloBundle/Form/Type/CompanyType.php
133133
public function buildForm(FormBuilderInterface $builder, array $options)

‎cookbook/form/unit_testing.rst

Copy file name to clipboardExpand all lines: cookbook/form/unit_testing.rst
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ The simplest ``TypeTestCase`` implementation looks like the following::
7373
}
7474
}
7575

76-
So, what does it test? Let's explain it line by line.
76+
So, what does it test? Here comes a detailed explanation.
7777

7878
First you verify if the ``FormType`` compiles. This includes basic class
7979
inheritance, the ``buildForm`` function and options resolution. This should

‎cookbook/routing/custom_route_loader.rst

Copy file name to clipboardExpand all lines: cookbook/routing/custom_route_loader.rst
+2-2Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -202,9 +202,9 @@ Instead, you only need to add a few extra lines to the routing configuration:
202202
return $collection;
203203
204204
The important part here is the ``type`` key. Its value should be "extra".
205-
This is the type which our ``ExtraLoader`` supports and this will make sure
205+
This is the type which the ``ExtraLoader`` supports and this will make sure
206206
its ``load()`` method gets called. The ``resource`` key is insignificant
207-
for the ``ExtraLoader``, so we set it to ".".
207+
for the ``ExtraLoader``, so it is set to ".".
208208

209209
.. note::
210210

‎cookbook/security/acl.rst

Copy file name to clipboardExpand all lines: cookbook/security/acl.rst
+2-2Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -87,8 +87,8 @@ Fortunately, there is a task for this. Simply run the following command:
8787
Getting Started
8888
---------------
8989

90-
Coming back to the small example from the beginning, let's implement ACL for
91-
it.
90+
Coming back to the small example from the beginning, you can now implement
91+
ACL for it.
9292

9393
Creating an ACL, and adding an ACE
9494
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

‎cookbook/security/acl_advanced.rst

Copy file name to clipboardExpand all lines: cookbook/security/acl_advanced.rst
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ Symfony2, there are basically two different scopes:
7777
it only applies to one specific object.
7878

7979
Sometimes, you will find the need to apply an ACE only to a specific field of
80-
the object. Let's say you want the ID only to be viewable by an administrator,
80+
the object. Suppose you want the ID only to be viewable by an administrator,
8181
but not by your customer service. To solve this common problem, two more sub-scopes
8282
have been added:
8383

‎cookbook/security/custom_provider.rst

Copy file name to clipboardExpand all lines: cookbook/security/custom_provider.rst
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ which defines a method to check if the user is equal to the current user. This
3333
interface requires an :method:`Symfony\\Component\\Security\\Core\\User\\EquatableInterface::isEqualTo`
3434
method.
3535

36-
Let's see this in action::
36+
This is how your ``WebserviceUser`` class looks in action::
3737

3838
// src/Acme/WebserviceUserBundle/Security/User/WebserviceUser.php
3939
namespace Acme\WebserviceUserBundle\Security\User;

‎cookbook/service_container/scopes.rst

Copy file name to clipboardExpand all lines: cookbook/service_container/scopes.rst
+6-6Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
.. index::
22
single: DependencyInjection; Scopes
33

4-
How to work with Scopes
4+
How to Work with Scopes
55
=======================
66

77
This entry is all about scopes, a somewhat advanced topic related to the
@@ -42,12 +42,12 @@ when compiling the container. Read the sidebar below for more details.
4242

4343
Imagine, however, that you need the ``request`` service in your ``my_mailer``
4444
service, maybe because you're reading the URL of the current request.
45-
So, you add it as a constructor argument. Let's look at why this presents
46-
a problem:
45+
So, you add it as a constructor argument. There are several reasons why
46+
this presents a problem:
4747

48-
* When requesting ``my_mailer``, an instance of ``my_mailer`` (let's call
49-
it *MailerA*) is created and the ``request`` service (let's call it
50-
*RequestA*) is passed to it. Life is good!
48+
* When requesting ``my_mailer``, an instance of ``my_mailer`` (called
49+
*MailerA*) is created and the ``request`` service (called *RequestA*)
50+
is passed to it. Life is good!
5151

5252
* You've now made a subrequest in Symfony, which is a fancy way of saying
5353
that you've called, for example, the ``{{ render(...) }}`` Twig function,

‎cookbook/symfony1.rst

Copy file name to clipboardExpand all lines: cookbook/symfony1.rst
+2-2Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -50,8 +50,8 @@ directory is a bit like the ``plugins`` directory in symfony1, but much more
5050
flexible. Additionally, while *your* bundles will live in the ``src/`` directory,
5151
third-party bundles will live somewhere in the ``vendor/`` directory.
5252

53-
To get a better picture of the ``src/`` directory, let's first think of a
54-
symfony1 application. First, part of your code likely lives inside one or
53+
To get a better picture of the ``src/`` directory, first think of the structure
54+
of a symfony1 application. First, part of your code likely lives inside one or
5555
more applications. Most commonly these include modules, but could also include
5656
any other PHP classes you put in your application. You may have also created
5757
a ``schema.yml`` file in the ``config`` directory of your project and built

‎cookbook/templating/PHP.rst

Copy file name to clipboardExpand all lines: cookbook/templating/PHP.rst
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,7 @@ is the same notation used to reference a template. The ``::`` part simply
100100
means that the controller element is empty, so the corresponding file is
101101
directly stored under ``views/``.
102102

103-
Now, let's have a look at the ``layout.html.php`` file:
103+
Now, have a look at the ``layout.html.php`` file:
104104

105105
.. code-block:: html+php
106106

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.