Mark -c and -O as command line options in reStructuredText. (GH-10103)

(cherry picked from commit ea6a28c9f7)

Co-authored-by: Andrés Delfino <adelfino@gmail.com>

Doc/reference/executionmodel.rst

@@ -22,7 +22,7 @@ The following are blocks: a module, a function body, and a class definition.
 Each command typed interactively is a block.  A script file (a file given as
 standard input to the interpreter or specified as a command line argument to the
 interpreter) is a code block.  A script command (a command specified on the
-interpreter command line with the '**-c**' option) is a code block.  The string
+interpreter command line with the :option:`-c` option) is a code block.  The string
 argument passed to the built-in functions :func:`eval` and :func:`exec` is a
 code block.
 

Doc/reference/import.rst

@@ -951,7 +951,7 @@ In :ref:`the remaining cases <using-on-interface-options>`
 :mod:`__main__` does not correspond directly with an importable module:
 
 - interactive prompt
-- -c switch
+- :option:`-c` option
 - running from stdin
 - running directly from a source or bytecode file
 

Doc/reference/simple_stmts.rst

@@ -402,7 +402,7 @@ The extended form, ``assert expression1, expression2``, is equivalent to ::
 These equivalences assume that :const:`__debug__` and :exc:`AssertionError` refer to
 the built-in variables with those names.  In the current implementation, the
 built-in variable :const:`__debug__` is ``True`` under normal circumstances,
-``False`` when optimization is requested (command line option -O).  The current
+``False`` when optimization is requested (command line option :option:`-O`).  The current
 code generator emits no code for an assert statement when optimization is
 requested at compile time.  Note that it is unnecessary to include the source
 code for the expression that failed in the error message; it will be displayed