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 ceca63f

Browse filesBrowse files
weaverryanweaverryan
committed
minor #4653 update ordered list syntax (xabbuh)
This PR was merged into the 2.3 branch. Discussion ---------- update ordered list syntax | Q | A | ------------- | --- | Doc fix? | yes | New docs? | no | Applies to | all | Fixed tickets | Commits ------- ee06eec update ordered list syntax
2 parents a137918 + ee06eec commit ceca63f
Copy full SHA for ceca63f

File tree

Expand file treeCollapse file tree

7 files changed

+44
-44
lines changed
Filter options
Expand file treeCollapse file tree

7 files changed

+44
-44
lines changed

‎book/translation.rst

Copy file name to clipboardExpand all lines: book/translation.rst
+3-3Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -394,13 +394,13 @@ Imagine that the user's locale is ``fr_FR`` and that you're translating the
394394
key ``Symfony is great``. To find the French translation, Symfony actually
395395
checks translation resources for several different locales:
396396

397-
1. First, Symfony looks for the translation in a ``fr_FR`` translation resource
397+
#. First, Symfony looks for the translation in a ``fr_FR`` translation resource
398398
(e.g. ``messages.fr_FR.xliff``);
399399

400-
2. If it wasn't found, Symfony looks for the translation in a ``fr`` translation
400+
#. If it wasn't found, Symfony looks for the translation in a ``fr`` translation
401401
resource (e.g. ``messages.fr.xliff``);
402402

403-
3. If the translation still isn't found, Symfony uses the ``fallback`` configuration
403+
#. If the translation still isn't found, Symfony uses the ``fallback`` configuration
404404
parameter, which defaults to ``en`` (see `Configuration`_).
405405

406406
.. _book-translation-user-locale:

‎components/routing/introduction.rst

Copy file name to clipboardExpand all lines: components/routing/introduction.rst
+7-7Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -72,25 +72,25 @@ Defining Routes
7272

7373
A full route definition can contain up to seven parts:
7474

75-
1. The URL path route. This is matched against the URL passed to the `RequestContext`,
75+
#. The URL path route. This is matched against the URL passed to the `RequestContext`,
7676
and can contain named wildcard placeholders (e.g. ``{placeholders}``)
7777
to match dynamic parts in the URL.
7878

79-
2. An array of default values. This contains an array of arbitrary values
79+
#. An array of default values. This contains an array of arbitrary values
8080
that will be returned when the request matches the route.
8181

82-
3. An array of requirements. These define constraints for the values of the
82+
#. An array of requirements. These define constraints for the values of the
8383
placeholders as regular expressions.
8484

85-
4. An array of options. These contain internal settings for the route and
85+
#. An array of options. These contain internal settings for the route and
8686
are the least commonly needed.
8787

88-
5. A host. This is matched against the host of the request. See
88+
#. A host. This is matched against the host of the request. See
8989
:doc:`/components/routing/hostname_pattern` for more details.
9090

91-
6. An array of schemes. These enforce a certain HTTP scheme (``http``, ``https``).
91+
#. An array of schemes. These enforce a certain HTTP scheme (``http``, ``https``).
9292

93-
7. An array of methods. These enforce a certain HTTP request method (``HEAD``,
93+
#. An array of methods. These enforce a certain HTTP request method (``HEAD``,
9494
``GET``, ``POST``, ...).
9595

9696
.. versionadded:: 2.2

‎components/serializer.rst

Copy file name to clipboardExpand all lines: components/serializer.rst
+3-3Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -144,9 +144,9 @@ of the ``Person`` class would be encoded in XML format::
144144
In this case, :method:`Symfony\\Component\\Serializer\\Serializer::deserialize`
145145
needs three parameters:
146146

147-
1. The information to be decoded
148-
2. The name of the class this information will be decoded to
149-
3. The encoder used to convert that information into an array
147+
#. The information to be decoded
148+
#. The name of the class this information will be decoded to
149+
#. The encoder used to convert that information into an array
150150

151151
Using Camelized Method Names for Underscored Attributes
152152
-------------------------------------------------------

‎components/translation/introduction.rst

Copy file name to clipboardExpand all lines: components/translation/introduction.rst
+3-3Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -159,12 +159,12 @@ If the message is not located in the catalog of the specific locale, the
159159
translator will look into the catalog of one or more fallback locales. For
160160
example, assume you're trying to translate into the ``fr_FR`` locale:
161161

162-
1. First, the translator looks for the translation in the ``fr_FR`` locale;
162+
#. First, the translator looks for the translation in the ``fr_FR`` locale;
163163

164-
2. If it wasn't found, the translator looks for the translation in the ``fr``
164+
#. If it wasn't found, the translator looks for the translation in the ``fr``
165165
locale;
166166

167-
3. If the translation still isn't found, the translator uses the one or more
167+
#. If the translation still isn't found, the translator uses the one or more
168168
fallback locales set explicitly on the translator.
169169

170170
For (3), the fallback locales can be set by calling

‎contributing/code/security.rst

Copy file name to clipboardExpand all lines: contributing/code/security.rst
+23-23Lines changed: 23 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -19,10 +19,10 @@ Resolving Process
1919
For each report, we first try to confirm the vulnerability. When it is
2020
confirmed, the core-team works on a solution following these steps:
2121

22-
1. Send an acknowledgement to the reporter;
23-
2. Work on a patch;
24-
3. Get a CVE identifier from mitre.org;
25-
4. Write a security announcement for the official Symfony `blog`_ about the
22+
#. Send an acknowledgement to the reporter;
23+
#. Work on a patch;
24+
#. Get a CVE identifier from mitre.org;
25+
#. Write a security announcement for the official Symfony `blog`_ about the
2626
vulnerability. This post should contain the following information:
2727

2828
* a title that always include the "Security release" string;
@@ -32,12 +32,12 @@ confirmed, the core-team works on a solution following these steps:
3232
* how to patch/upgrade/workaround affected applications;
3333
* the CVE identifier;
3434
* credits.
35-
5. Send the patch and the announcement to the reporter for review;
36-
6. Apply the patch to all maintained versions of Symfony;
37-
7. Package new versions for all affected versions;
38-
8. Publish the post on the official Symfony `blog`_ (it must also be added to
35+
#. Send the patch and the announcement to the reporter for review;
36+
#. Apply the patch to all maintained versions of Symfony;
37+
#. Package new versions for all affected versions;
38+
#. Publish the post on the official Symfony `blog`_ (it must also be added to
3939
the "`Security Advisories`_" category);
40-
9. Update the security advisory list (see below).
40+
#. Update the security advisory list (see below).
4141

4242
.. note::
4343

@@ -61,23 +61,23 @@ As Symfony is used by many large Open-Source projects, we standardized the way
6161
the Symfony security team collaborates on security issues with downstream
6262
projects. The process works as follows:
6363

64-
1. After the Symfony security team has acknowledged a security issue, it
65-
immediately sends an email to the downstream project security teams to inform
66-
them of the issue;
64+
#. After the Symfony security team has acknowledged a security issue, it
65+
immediately sends an email to the downstream project security teams to
66+
inform them of the issue;
6767

68-
2. The Symfony security team creates a private Git repository to ease the
69-
collaboration on the issue and access to this repository is given to the
70-
Symfony security team, to the Symfony contributors that are impacted by the
71-
issue, and to one representative of each downstream projects;
68+
#. The Symfony security team creates a private Git repository to ease the
69+
collaboration on the issue and access to this repository is given to the
70+
Symfony security team, to the Symfony contributors that are impacted by
71+
the issue, and to one representative of each downstream projects;
7272

73-
3. All people with access to the private repository work on a solution to
74-
solve the issue via pull requests, code reviews, and comments;
73+
#. All people with access to the private repository work on a solution to
74+
solve the issue via pull requests, code reviews, and comments;
7575

76-
4. Once the fix is found, all involved projects collaborate to find the best
77-
date for a joint release (there is no guarantee that all releases will be at
78-
the same time but we will try hard to make them at about the same time). When
79-
the issue is not known to be exploited in the wild, a period of two weeks
80-
seems like a reasonable amount of time.
76+
#. Once the fix is found, all involved projects collaborate to find the best
77+
date for a joint release (there is no guarantee that all releases will
78+
be at the same time but we will try hard to make them at about the same
79+
time). When the issue is not known to be exploited in the wild, a period
80+
of two weeks seems like a reasonable amount of time.
8181

8282
The list of downstream projects participating in this process is kept as small
8383
as possible in order to better manage the flow of confidential information

‎cookbook/deployment/heroku.rst

Copy file name to clipboardExpand all lines: cookbook/deployment/heroku.rst
+2-2Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -81,9 +81,9 @@ Creating a Procfile
8181
By default, Heroku will launch an Apache web server together with PHP to serve
8282
applications. However, two special circumstances apply to Symfony applications:
8383

84-
1. The document root is in the ``web/`` directory and not in the root directory
84+
#. The document root is in the ``web/`` directory and not in the root directory
8585
of the application;
86-
2. The Composer ``bin-dir``, where vendor binaries (and thus Heroku's own boot
86+
#. The Composer ``bin-dir``, where vendor binaries (and thus Heroku's own boot
8787
scripts) are placed, is ``bin/`` , and not the default ``vendor/bin``.
8888

8989
.. note::

‎cookbook/security/custom_authentication_provider.rst

Copy file name to clipboardExpand all lines: cookbook/security/custom_authentication_provider.rst
+3-3Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,9 +20,9 @@ The following chapter demonstrates how to create a custom authentication
2020
provider for WSSE authentication. The security protocol for WSSE provides
2121
several security benefits:
2222

23-
1. Username / Password encryption
24-
2. Safe guarding against replay attacks
25-
3. No web server configuration required
23+
#. Username / Password encryption
24+
#. Safe guarding against replay attacks
25+
#. No web server configuration required
2626

2727
WSSE is very useful for the securing of web services, may they be SOAP or
2828
REST.

0 commit comments

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