Implement suggestions by @phackstock

IAMconsortium · Jul 3, 2023 · 38cf531 · 38cf531
1 parent a30564e
commit 38cf531
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/docs/user_guide/model-mapping.rst b/docs/user_guide/model-mapping.rst
@@ -49,7 +49,7 @@ required in a valid model mapping. See :ref:`region` for more information.
    These constituent regions must be model native regions.
 
    The names of the constituent regions **must** refer to the **original** model native
-   region names, i.e., *region_a* and *region_b* and **not** *alternative_name_a*
+   region names, i.e., *region_a* and *region_b*, **not** *alternative_name_a*
    in the example shown above.
 
 * *exclude_regions* optional (list of str): If input data for region processing contains

diff --git a/docs/user_guide/model-registration.rst b/docs/user_guide/model-registration.rst
@@ -43,10 +43,10 @@ national countries), add a file ``<your-model_vX.X>.yaml`` in the folder
 This file should follow the region-naming conventions of :ref:`region`.
 The *hierarchy* property should be the model name inluding the version number.
 
-Region-processing mapping
-^^^^^^^^^^^^^^^^^^^^^^^^^
+Model mapping for region processing
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-If the scenario-processing workflow should execute a region-aggregation step,
+If the scenario-processing workflow should execute a region-processing step,
 add a file ``<your-model_vX.X>.yaml`` in the folder ``mappings/``.
 
 This file should follow the region-naming conventions of :ref:`model_mapping`.