  That's where caching comes in.
  
  To cache something is to save the result of an expensive calculation so that
  you don't have to perform the calculation next time. Here's some pseudocode
  explaining how this would work for a dynamically generated web page::
  
      given a URL, try finding that page in the cache
      if the page is in the cache:
          return the cached page
      else:
 
</s> remove equivalent to evaluating::
 </s> add equivalent to evaluating:

.. code-block:: text </s> remove         # ...
 </s> add         ... </s> remove         def fancy_utility_function(s, ...):
 </s> add         def fancy_utility_function(s, *args, **kwargs): </s> remove like so::
 </s> add like so:

.. code-block:: pycon </s> remove 32-bit, 8 character digest in the constraint name; for example::
 </s> add 32-bit, 8 character digest in the constraint name; for example:

.. code-block:: sql
explaining how this would work for a dynamically generated web page:

.. code-block:: text
  That's where caching comes in.
  
  To cache something is to save the result of an expensive calculation so that
  you don't have to perform the calculation next time. Here's some pseudocode
explaining how this would work for a dynamically generated web page:

.. code-block:: text
  
      given a URL, try finding that page in the cache
      if the page is in the cache:
          return the cached page
      else:
keep keep keep keep replace keep keep keep keep keep
 Refs #34140 -- Corrected rst code-block and various formatting issues in docs. 
docs/topics/cache.txt