From 7b068c6beaf08092941ca67a1c403ce30c60f08c Mon Sep 17 00:00:00 2001 From: Andy Snell Date: Sun, 15 Mar 2020 20:49:09 -0500 Subject: [PATCH] Fix Minor Typos in Docs --- docs/database.rst | 4 ++-- docs/upgrading/3-to-4.rst | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/database.rst b/docs/database.rst index 8b859f39..3607dfda 100644 --- a/docs/database.rst +++ b/docs/database.rst @@ -101,7 +101,7 @@ this (again, assume some of the variables in this example have been set beforehand): .. code-block:: php - :caption: Store a string UUID to the uuid column + :caption: Store UUID bytes to the uuid column :name: database.uuid-bytes-store-example $sth->execute([ @@ -186,7 +186,7 @@ with this approach, but there are a couple of points to consider: We'll deal with the first point in the section, :ref:`database.order`. For the second point, if you are using the string version of the UUID (i.e., ``char(36)``), then not only will the primary key be large and take up a lot of -space, but every secondary key that uses that primary key will also be must +space, but every secondary key that uses that primary key will also be much larger. For this reason, if you choose to use UUIDs as primary keys, it might be worth diff --git a/docs/upgrading/3-to-4.rst b/docs/upgrading/3-to-4.rst index f89e4edb..fa8b1817 100644 --- a/docs/upgrading/3-to-4.rst +++ b/docs/upgrading/3-to-4.rst @@ -33,7 +33,7 @@ There are a lot of new features in ramsey/uuid! Here are a few of them: * :php:class:`Rfc4122\\UuidV3 ` * :php:class:`Rfc4122\\UuidV4 ` * :php:class:`Rfc4122\\UuidV5 ` - * Rfc4122\\NilUuid + * :php:class:`Rfc4122\\NilUuid ` * Add classes to represent version 6 UUIDs, GUIDs, and nonstandard (non-RFC 4122 variants) UUIDs: