Merge branch '5.2' into 5.x

* 5.2:
  Minor tweak
  Fix markdown in multiple_entity_managers.rst
  [Intl] Remove duplicated parentheses
  Update bc.rst

Author: javiereguiluz

components/intl.rst

@@ -353,8 +353,8 @@ arguments to get the offset at any given point in time::
 The string representation of the GMT offset can vary depending on the locale, so
 you can pass the locale as the third optional argument::
 
-    $offset = Timezones::getGmtOffset('Europe/Madrid', strtotime('October 28, 2019'), 'ar')); // $offset = 'غرينتش+01:00'
-    $offset = Timezones::getGmtOffset('Europe/Madrid', strtotime('October 28, 2019'), 'dz')); // $offset = 'ཇི་ཨེམ་ཏི་+01:00'
+    $offset = Timezones::getGmtOffset('Europe/Madrid', strtotime('October 28, 2019'), 'ar'); // $offset = 'غرينتش+01:00'
+    $offset = Timezones::getGmtOffset('Europe/Madrid', strtotime('October 28, 2019'), 'dz'); // $offset = 'ཇི་ཨེམ་ཏི་+01:00'
 
 If the given timezone ID doesn't exist, the methods trigger a
 :class:`Symfony\\Component\\Intl\\Exception\\MissingResourceException`. In addition

contributing/code/bc.rst

@@ -4,10 +4,13 @@ Our Backward Compatibility Promise
 Ensuring smooth upgrades of your projects is our first priority. That's why
 we promise you backward compatibility (BC) for all minor Symfony releases.
 You probably recognize this strategy as `Semantic Versioning`_. In short,
-Semantic Versioning means that only major releases (such as 2.0, 3.0 etc.) are
-allowed to break backward compatibility. Minor releases (such as 2.5, 2.6 etc.)
+Semantic Versioning means that only major releases (such as 5.0, 6.0 etc.) are
+allowed to break backward compatibility. Minor releases (such as 5.1, 5.2 etc.)
 may introduce new features, but must do so without breaking the existing API of
-that release branch (2.x in the previous example).
+that release branch (5.x in the previous example).
+
+We also provide deprecation message triggered in the code base to help you with
+the migration process across major release.
 
 .. caution::
 

doctrine/multiple_entity_managers.rst

@@ -320,6 +320,6 @@ The same applies to repository calls::
             // ...
         }
 
-	You should now always fetch this repository using ``ManagerRegistry::getRepository()``.
+    You should now always fetch this repository using ``ManagerRegistry::getRepository()``.
 
 .. _`several alternatives`: https://stackoverflow.com/a/11494543