Clarify language in directives regarding named attribute usage in version comparisons.

Signed-off-by: Jos Verlinde <Jos_Verlinde@hotmail.com>

Author: Josverl

docs/spec/directives.rst

@@ -177,7 +177,7 @@ Type checkers should support the following comparison patterns:
     * ``sys.version_info < <2-tuple>``
 
 Comparisons checks are only supported against the first two elements of the version tuple. 
-Use of named attributes is not supported.
+Use of named attributes is not mandated.
 
 .. code-block:: python
    :caption: Example `sys.version_info`
@@ -244,7 +244,7 @@ Type checkers should support the following comparison patterns:
     * ``sys.implementation.version < <2-tuple>``
 
 Comparisons checks are only supported against the first two elements of the implementation version tuple.
-Use of named attributes is not supported.
+Use of named attributes is not mandated.
 
 .. code-block:: python
    :caption: Example `sys.implementation.version`
@@ -266,7 +266,7 @@ No support for complex expressions
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 Type checkers are only required to support the above patterns, and are not required to evaluate complex expressions involving these variables.
-For example, the pattern ``sys.platform == "linux"`` is supported but other syntax variants such as ``platform == "linux"`` and ``"win" not in sys.platform`` are not supported.
+For example, the pattern ``sys.platform == "linux"`` is supported but other syntax variants such as ``platform == "linux"`` and ``"win" not in sys.platform`` are not mandated.
 
 Therefore checkers are **not required** to understand obfuscations such as: