@@ -3,11 +3,12 @@ Our Backwards Compatibility Promise
33
44As of Symfony 2.3, we promise you backwards compatibility for all further 2.x
55releases. Ensuring smooth upgrades of your projects is our first priority.
6- However, backwards compatibility comes in many different flavors. This page
7- lists which code changes are covered by our promise and to what degree.
6+ However, backwards compatibility comes in many different flavors.
87
9- If you are contributing to Symfony, make sure that your code changes comply to
10- the rules listed below.
8+ This page has two different target audiences: If you are using Symfony, it will
9+ tell you how to make sure that you will be able to upgrade smoothly to all
10+ future 2.x versions. If you are contributing, this page will tell you the rules
11+ you need to follow to ensure smooth upgrades for our users.
1112
1213..note ::
1314
@@ -230,7 +231,7 @@ Change return type Yes [2]_ [4]_ No
230231 however be documented in the UPGRADE file.
231232
2322332 ]Should be avoided. When done, this change must be documented in the
233- UGPRADE file.
234+ UPGRADE file.
234235
2352363 ]Only the last parameter(s) of a method may be removed.
236237