Skip to content

Commit ca1e7df

Browse files
committed
[#4611] A few more tweaks and fixes
1 parent e6b3f13 commit ca1e7df

File tree

1 file changed

+18
-17
lines changed

1 file changed

+18
-17
lines changed

cookbook/upgrading.rst

Lines changed: 18 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -24,12 +24,13 @@ then it's *really* easy:
2424
2525
That's it! You should not encounter any backwards-compatibility breaks or
2626
need to change anything else in your code. That's because when you started
27-
your Symfony project, your ``composer.json`` included Symfony using a constraint
28-
such as ``2.6.*``, where only the *last* version number changes when you update.
27+
your project, your ``composer.json`` included Symfony using a constraint
28+
like ``2.6.*``, where only the *last* version number will change when you
29+
update.
2930

3031
You may also want to upgrade the rest of your libraries. If you've done a
31-
good job with your version constraints in ``composer.json``, you can do this
32-
safely by running:
32+
good job with your `version constraints`_ in ``composer.json``, you can do
33+
this safely by running:
3334

3435
.. code-block:: bash
3536
@@ -41,7 +42,7 @@ to new versions that contain backwards-compatibility breaking changes.
4142

4243
.. _upgrading-minor-version:
4344

44-
Upgrading a Minor Version (e.g. 2.5.3 to 2.6.0)
45+
Upgrading a Minor Version (e.g. 2.5.3 to 2.6.1)
4546
-----------------------------------------------
4647

4748
If you're upgrading a minor version (where the middle number changes), then
@@ -53,16 +54,16 @@ in a second how to prepare for them.
5354

5455
There are two steps to upgrading:
5556

56-
#. :ref:`upgrade-minor-symfony-composer`;
57-
#. :ref:`upgrade-minor-symfony-code`, which includes instructions for each version.
57+
:ref:`upgrade-minor-symfony-composer`;
58+
:ref:`upgrade-minor-symfony-code`
5859

5960
.. _`upgrade-minor-symfony-composer`:
6061

61-
Update the Symfony Library via Composer
62-
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
62+
1) Update the Symfony Library via Composer
63+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
6364

64-
First, you need to update Symfony by modifying your ``composer.json`` to
65-
use the new version:
65+
First, you need to update Symfony by modifying your ``composer.json`` file
66+
to use the new version:
6667

6768
.. code-block:: json
6869
@@ -71,7 +72,7 @@ use the new version:
7172
7273
"require": {
7374
"php": ">=5.3.3",
74-
"symfony/symfony": "~2.6.*",
75+
"symfony/symfony": "2.6.*",
7576
"...": "... no changes to anything else..."
7677
},
7778
"...": "...",
@@ -84,8 +85,8 @@ Next, use Composer to download new versions of the libraries:
8485
$ composer update symfony/symfony
8586
8687
You may also want to upgrade the rest of your libraries. If you've done a
87-
good job with your version constraints in ``composer.json``, you can do this
88-
safely by running:
88+
good job with your `version constraints`_ in ``composer.json``, you can do
89+
this safely by running:
8990

9091
.. code-block:: bash
9192
@@ -97,8 +98,8 @@ to new versions that contain backwards-compatibility breaking changes.
9798

9899
.. _`upgrade-minor-symfony-code`:
99100

100-
Updating Your Code to Work with the new Version
101-
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
101+
2) Updating Your Code to Work with the new Version
102+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
102103

103104
In theory, you should be done! However, you *may* need to make a few changes
104105
to your code to get everything working. Additionally, some features you're
@@ -112,7 +113,7 @@ to read to see if you need any code changes.
112113

113114
.. tip::
114115

115-
Don't see the version here that you're upgrading too? Just find the
116+
Don't see the version here that you're upgrading to? Just find the
116117
UPGRADE-X.X.md file for the appropriate version on the `Symfony Repository`_.
117118

118119
Upgrading to Symfony 2.6

0 commit comments

Comments
 (0)