Reword

Author: javiereguiluz

http_cache/expiration.rst

@@ -38,10 +38,12 @@ additional directives):
 
 .. note::
 
-    Using the ``setSharedMaxAge()`` may seem equivalent to using both ``setPublic()``
-    and ``setMaxAge()`` methods. However, their behavior is different in a
-    ``stale-if-error`` scenario and that's why it's recommended to use both
-    ``public`` and ``max-age`` directives.
+    Using the ``setSharedMaxAge()`` method is not equivalent to using both
+    ``setPublic()`` and ``setMaxAge()`` methods. According to the
+    `Serving Stale Responses`_ section of RFC 7234, the ``s-maxage`` setting
+    (added by ``setSharedMaxAge()`` method) prohibits a cache to use a stale
+    response in ``stale-if-error`` scenarios. That's why it's recommended to use
+    both ``public`` and ``max-age`` directives.
 
 .. index::
     single: Cache; Expires header
@@ -84,9 +86,10 @@ servers should not send ``Expires`` dates more than one year in the future."
 
 .. note::
 
-    According to `RFC 7234 - Caching`_, the ``Expires`` header value is ignored
-    when the ``s-maxage`` or ``max-age`` directive of the ``Cache-Control``
-    header is defined.
+    According to the `Calculating Freshness Lifetime`_ section of RFC 7234,
+    the ``Expires`` header value is ignored when the ``s-maxage`` or ``max-age``
+    directive of the ``Cache-Control`` header is defined.
 
 .. _`expiration model`: https://tools.ietf.org/html/rfc2616#section-13.2
-.. _`RFC 7234 - Caching`: https://tools.ietf.org/html/rfc7234#section-4.2.1
+.. _`Calculating Freshness Lifetime`: https://tools.ietf.org/html/rfc7234#section-4.2.1
+.. _`Serving Stale Responses`: https://tools.ietf.org/html/rfc7234#section-4.2.4