Fix documentation build and broken link

doc/quickstart/find_data.rst

@@ -401,7 +401,7 @@ unstructured grids, which is required by many software packages or tools to
 work correctly and specifically by Iris to interpret the grid as a
 :ref:`mesh <iris:ugrid>`.
 An example is the horizontal regridding of native ICON data to a regular grid.
-While the :ref:`built-in regridding schemes <built-in regridding schemes>`
+While the :ref:`built-in regridding schemes <default regridding schemes>`
 `linear` and `nearest`  can handle unstructured grids (i.e., not UGRID-compliant) and meshes (i.e., UGRID-compliant),
 the `area_weighted` scheme requires the input data in UGRID format.
 This automatic UGRIDization is enabled by default, but can be switched off with
@@ -559,7 +559,7 @@ model output.
 
 .. warning::
 
-  This is the first version of ACCESS-ESM CMORizer for ESMValCore. Currently, 
+  This is the first version of ACCESS-ESM CMORizer for ESMValCore. Currently,
   Supported variables: ``pr``, ``ps``, ``psl``, ``rlds``, ``tas``, ``ta``, ``va``,
   ``ua``, ``zg``, ``hus``, ``clt``, ``rsus``, ``rlus``.
 
@@ -570,7 +570,7 @@ The default naming conventions for input directories and files for ACCESS output
 
 .. hint::
 
-  We only provide one default `input_dir` since this is how ACCESS-ESM native data was 
+  We only provide one default `input_dir` since this is how ACCESS-ESM native data was
   stored on NCI. Users can modify this path in the :ref:`config-developer` to match their local file structure.
 
 
@@ -579,7 +579,7 @@ Thus, example dataset entries could look like this:
 .. code-block:: yaml
 
   dataset:
-    - {project: ACCESS, mip: Amon, dataset:ACCESS_ESM1_5, sub_dataset: HI-CN-05, 
+    - {project: ACCESS, mip: Amon, dataset:ACCESS_ESM1_5, sub_dataset: HI-CN-05,
       exp: history, modeling_realm: atm, special_attr: pa, start_year: 1986, end_year: 1986}
 
 
@@ -597,15 +597,15 @@ Key                  Description                            Default value if not
 ==================== ====================================== =================================
 ``raw_name``         Variable name of the variable in the   CMOR variable name of the
                      raw input file                         corresponding variable
-``modeling_realm``   Realm attribute include `atm`, `ice`   No default (needs to be 
+``modeling_realm``   Realm attribute include `atm`, `ice`   No default (needs to be
                      and `oce`                              specified in extra facets or
                                                             recipe if default DRS is used)
 ```special_attr``    A special attribute in the filename    No default
-                     `ACCESS-ESM` raw data, it's related to 
+                     `ACCESS-ESM` raw data, it's related to
                      frquency of raw data
 ``sub_dataset``      Part of the ACCESS-ESM raw dataset     No default
                      root, need to specify if you want to
-                     use the cmoriser                                                                       
+                     use the cmoriser
 ==================== ====================================== =================================
 
 .. _data-retrieval:
@@ -845,7 +845,7 @@ about this since we can point the user to the specific functionality
 `here <https://scitools-iris.readthedocs.io/en/latest/userguide/loading_iris_cubes.html>`_ but we will underline
 that the initial loading is done by adhering to the CF Conventions that `iris` operates by as well (see
 `CF Conventions Document <http://cfconventions.org/cf-conventions/cf-conventions.html>`_ and the search
-page for CF `standard names <http://cfconventions.org/standard-names.html>`_).
+page for CF `standard names <https://cfconventions.org/Data/cf-standard-names/current/build/cf-standard-name-table.html>`_).
 
 Data concatenation from multiple sources
 ========================================