Fix some incorrect rst markups

docs/pages/advanced_topics/input_hooks.rst

@@ -14,7 +14,7 @@ As a consequence, we will "trampoline" back and forth between two event loops.
 
 .. note::
 
-    This will use a :class:`~asyncio.SelectorEventLoop`, not the :class:
+    This will use a :class:`~asyncio.SelectorEventLoop`, not the
     :class:`~asyncio.ProactorEventLoop` (on Windows) due to the way the
     implementation works (contributions are welcome to make that work).
 

docs/pages/asking_for_a_choice.rst

@@ -1,4 +1,4 @@
-.. _asking_for_input:
+.. _asking_for_a_choice:
 
 Asking for a choice
 ===================

docs/pages/full_screen_apps.rst

@@ -68,10 +68,10 @@ I/O objects
 Every :class:`~prompt_toolkit.application.Application` instance requires an I/O
 object for input and output:
 
-    - An :class:`~prompt_toolkit.input.Input` instance, which is an abstraction
-      of the input stream (stdin).
-    - An :class:`~prompt_toolkit.output.Output` instance, which is an
-      abstraction of the output stream, and is called by the renderer.
+- An :class:`~prompt_toolkit.input.Input` instance, which is an abstraction
+  of the input stream (stdin).
+- An :class:`~prompt_toolkit.output.Output` instance, which is an
+  abstraction of the output stream, and is called by the renderer.
 
 Both are optional and normally not needed to pass explicitly. Usually, the
 default works fine.

src/prompt_toolkit/application/application.py

@@ -169,7 +169,7 @@ class Application(Generic[_AppResult]):
     :param output: :class:`~prompt_toolkit.output.Output` instance. (Probably
                    Vt100_Output or Win32Output.)
 
-    Usage:
+    Usage::
 
         app = Application(...)
         app.run()

src/prompt_toolkit/eventloop/inputhook.py

@@ -94,7 +94,7 @@ def set_eventloop_with_inputhook(
 
 class InputHookSelector(BaseSelector):
     """
-    Usage:
+    Usage::
 
         selector = selectors.SelectSelector()
         loop = asyncio.SelectorEventLoop(InputHookSelector(selector, inputhook))