apply review suggestions

Author: garak

components/clock.rst

@@ -75,29 +75,6 @@ When using the Clock component, you manipulate
 :class:`Symfony\\Component\\Clock\\DatePoint` instances. You can learn more
 about it in :ref:`the dedicated section <clock_date-point>`.
 
-Storing DatePoints in Databases
--------------------------------
-
-If you :doc:`use Doctrine </doctrine>`, consider using the ``date_point`` Doctrine
-type, which converts to/from DatePoint objects automatically::
-
-    // src/Entity/Product.php
-    namespace App\Entity;
-
-    use Doctrine\ORM\Mapping as ORM;
-    use Symfony\Bridge\Doctrine\Types\DatePointType;
-    use Symfony\Component\Clock\DatePoint;
-
-    #[ORM\Entity(repositoryClass: ProductRepository::class)]
-    class Product
-    {
-        #[ORM\Column(type: DatePointType::NAME)]
-        private DatePoint $created;
-
-        // ...
-    }
-
-
 Available Clocks Implementations
 --------------------------------
 
@@ -292,6 +269,31 @@ timestamps::
 
 .. _clock_writing-tests:
 
+Storing DatePoints in Databases
+-------------------------------
+
+If you :doc:`use Doctrine </doctrine>`, consider using the ``date_point`` Doctrine
+type, which converts to/from ``DatePoint`` objects automatically::
+
+    // src/Entity/Product.php
+    namespace App\Entity;
+
+    use Doctrine\ORM\Mapping as ORM;
+    use Symfony\Component\Clock\DatePoint;
+
+    #[ORM\Entity]
+    class Product
+    {
+        #[ORM\Column]
+        private DatePoint $created;
+
+        // ...
+    }
+
+.. versionadded:: 7.3
+    The `DatePointType` was introduced in Symfony 7.3.
+
+
 Writing Time-Sensitive Tests
 ----------------------------