Merge branch '5.2' into 5.x

* 5.2:
  [Uid] Add note about ULIDs not being random in one case
  s/it's/its
  [Serializer] Fixed occurence of an old FQCN notation

Author: javiereguiluz

components/serializer.rst

@@ -174,6 +174,8 @@ when this happens, set the ``AbstractNormalizer::ALLOW_EXTRA_ATTRIBUTES`` contex
 ``false`` and provide an object that implements ``ClassMetadataFactoryInterface``
 when constructing the normalizer::
 
+    use App\Model\Person;
+
     $data = <<<EOF
     <person>
         <name>foo</name>
@@ -189,7 +191,7 @@ when constructing the normalizer::
 
     // this will throw a Symfony\Component\Serializer\Exception\ExtraAttributesException
     // because "city" is not an attribute of the Person class
-    $person = $serializer->deserialize($data, 'App\Model\Person', 'xml', [
+    $person = $serializer->deserialize($data, Person::class, 'xml', [
         AbstractNormalizer::ALLOW_EXTRA_ATTRIBUTES => false,
     ]);
 

components/uid.rst

@@ -238,6 +238,13 @@ ULIDs are an alternative to UUIDs when using those is impractical. They provide
 128-bit compatibility with UUID, they are lexicographically sortable and they
 are encoded as 26-character strings (vs 36-character UUIDs).
 
+.. note::
+
+    If you generate more than one ULID during the same millisecond in the
+    same process then the random portion is incremented by one bit in order
+    to provide monotonicity for sorting. The random portion is not random
+    compared to the previous ULID in this case.
+
 Generating ULIDs
 ~~~~~~~~~~~~~~~~
 

workflow.rst

@@ -160,7 +160,7 @@ like this:
     If you are creating your first workflows, consider using the ``workflow:dump``
     command to :doc:`debug the workflow contents </workflow/dumping-workflows>`.
 
-The configured property will be used via it's implemented getter/setter methods by the marking store::
+The configured property will be used via its implemented getter/setter methods by the marking store::
 
     // src/Entity/BlogPost.php
     namespace App\Entity;