fixed dataclasses.dataclass ref, removed ellipsis from optional refs …

…in command_line.rst Signed-off-by: Oleg Höfling <oleg.hoefling@gmail.com>
python · gvanrossum · Oct 8, 2019 · Oct 7, 2019 · Oct 7, 2019 · Oct 7, 2019
commit 58894fe1d4d8f35c788f7979d66d1360a5cf223a
diff --git a/docs/source/additional_features.rst b/docs/source/additional_features.rst
@@ -75,7 +75,7 @@ Caveats/Known Issues
 Some functions in the :py:mod:`dataclasses` module, such as :py:func:`~dataclasses.replace` and :py:func:`~dataclasses.asdict`,
 have imprecise (too permissive) types. This will be fixed in future releases.
 
-Mypy does not yet recognize aliases of :py:func:`dataclasses.dataclass`, and will
+Mypy does not yet recognize aliases of :py:func:`dataclasses.dataclass <dataclasses.dataclass>`, and will
 probably never recognize dynamically computed decorators. The following examples
 do **not** work:
 

diff --git a/docs/source/command_line.rst b/docs/source/command_line.rst
@@ -292,7 +292,7 @@ For more details, see :ref:`no_strict_optional`.
 
 ``--no-implicit-optional``
     This flag causes mypy to stop treating arguments with a ``None``
-    default value as having an implicit :py:data:`Optional[...] <typing.Optional>` type.
+    default value as having an implicit :py:data:`~typing.Optional` type.
 
     For example, by default mypy will assume that the ``x`` parameter
     is of type ``Optional[int]`` in the code snippet below since
@@ -312,7 +312,7 @@ For more details, see :ref:`no_strict_optional`.
             print(x)
 
 ``--no-strict-optional``
-    This flag disables strict checking of :py:data:`Optional[...] <typing.Optional>`
+    This flag disables strict checking of :py:data:`~typing.Optional`
     types and ``None`` values. With this option, mypy doesn't
     generally check the use of ``None`` values -- they are valid
     everywhere. See :ref:`no_strict_optional` for more about this feature.