chore(quickstart): correctly format "TextInput" in the Modals section (#640)

* docs: add migration docs for 4.1

* docs: detail message content intent in migration

* ADMIN/chore: finish catchup from rebase (#573)

* docs: add migration docs for 4.1

* docs: detail message content intent in migration

* ADMIN/chore: finish catchup from rebase (#573) (#574)

* docs: add migration docs for 4.1

* docs: detail message content intent in migration

* chore(quickstart): correctly format "TextInput" in the Modals section of the quickstart documentation

Co-authored-by: fl0w <41456914+goverfl0w@users.noreply.github.com>
Co-authored-by: James Walston <officialdeltadev@gmail.com>

Author: Nanrech

docs/quickstart.rst

@@ -337,7 +337,7 @@ tables, if you so wish to choose to not use our class objects instead.
 
 Creating a TextInput
 ^^^^^^^^^^^^^^^^^^^^
-You want to get a Text from a user? You can use ``TextInput``s for that.
+You want to get a Text from a user? You can use ``TextInput`` for that.
 
 .. code-block:: python
 
@@ -354,7 +354,7 @@ But how to send it? You can't use ``ctx.send`` for it. Take a look at :ref:`Moda
 
 Modals
 ******
-Modals are a new way to interact with a user. Currently only a ``TextInput`` component is supported. You can have up to three ``TextInput``s in a Modal.
+Modals are a new way to interact with a user. Currently only a ``TextInput`` component is supported. You can have up to three ``TextInput`` in a Modal.
 
 .. code-block:: python