Fix inconsistent strict_optional documentation

Author: BHUVANSH855

docs/source/command_line.rst

@@ -466,7 +466,8 @@ The following flags adjust how mypy handles values of type ``None``.
     .. warning::
 
         ``--no-strict-optional`` is evil. Avoid using it and definitely do
-        not use it without understanding what it does.
+        not use it without understanding what it does. See
+        :ref:`Kinds of types <strict_optional>` for more information.
 
 
 .. _configuring-warnings:

docs/source/config_file.rst

@@ -618,15 +618,17 @@ section of the command line docs.
     :type: boolean
     :default: True
 
-    Effectively disables checking of optional
-    types and ``None`` values. With this option, mypy doesn't
-    generally check the use of ``None`` values -- it is treated
-    as compatible with every type.
+    Enables checking of optional types and ``None`` values.
+    Setting this option to ``false`` effectively disables checking
+    of optional types and ``None`` values. With
+    ``strict_optional = false``, mypy doesn't generally check the use
+    of ``None`` values -- it is treated as compatible with every type.
 
     .. warning::
 
         ``strict_optional = false`` is evil. Avoid using it and definitely do
-        not use it without understanding what it does.
+        not use it without understanding what it does. See
+        :ref:`Kinds of types <strict_optional>` for more information.
 
 
 Configuring warnings