Merge pull request #430 from nens/release-june-2024-pt2

Fix broken anchors and references

source/a_releasenotes_3di_api.rst

@@ -3,7 +3,7 @@
 3Di API
 -------
 
-.. _release_notes_3di_api_20240530
+.. _release_notes_3di_api_20240530:
 
 May 30, 2024
 ^^^^^^^^^^^^
@@ -46,7 +46,7 @@ April 29, 2024
 
 
 March 18, 2024
-^^^^^^^^^^^^^
+^^^^^^^^^^^^^^
 
 - Add water quality settings and substance settings.
 

source/a_releasenotes_3di_live.rst

@@ -3,7 +3,7 @@
 3Di Live
 --------
 
-.. _release_notes_3di_live_20240605
+.. _release_notes_3di_live_20240605:
 
 June 5th, 2024
 ^^^^^^^^^^^^^^

source/a_releasenotes_3di_mi.rst

@@ -3,7 +3,7 @@
 3Di Modeller Interface
 ----------------------
 
-.. _release_notes_mi_20230605
+.. _release_notes_mi_20230605:
 
 June 5th, 2024
 ^^^^^^^^^^^^^^

source/a_releasenotes_computational_core.rst

@@ -3,7 +3,7 @@
 3Di Computational core
 ----------------------
 
-.. _release_notes_calccore_20240605
+.. _release_notes_calccore_20240605:
 
 June 5, 2024
 ^^^^^^^^^^^^
@@ -15,7 +15,7 @@ June 5, 2024
 - Bugfix: Load entering via leakage not included in substance summary (#808)
 
 
-.. _release_notes_calccore_20240530
+.. _release_notes_calccore_20240530:
 
 May 30, 2024
 ^^^^^^^^^^^^
@@ -38,7 +38,7 @@ April 29, 2024
 
 
 March 18, 2024
-^^^^^^^^^^^^^
+^^^^^^^^^^^^^^
 
 - Add substance settings to water quality module.
 

source/d_overview_management_portal.rst

@@ -135,7 +135,8 @@ If a new user needs access to 3Di from the organisation, this can be granted by
 
 #. Select the roles the user will have (see :ref:`roles`)
 #. Click *SAVE*.
-#. Success! The invitation has been sent and will be in the new user's mailbox within 5 minutes. An existing user can use the invitation link to accept the invitation. 
+#. Success! The invitation has been sent and will be in the new user's mailbox within 5 minutes. An existing user can use the invitation link to accept the invitation.
+
 A new user can create an account by using the :ref:`a_singing_up` guide. When accepted, the user will appear in the *User Management* overview.
 
 .. tip:: Clicking 🛈 will also show you an overview of the roles and the rights associated with them.
@@ -172,6 +173,7 @@ You cannot revoke your own *Manager* role.
 
 
 .. _roles:
+
 User roles
 ----------
 

source/e_results_analysis_tutorial.rst

@@ -309,7 +309,7 @@ The maximum water depth map gives insight in *where* the flooding occurs, but do
 #) Look at the graph. When does the water level start rising? When does the peak occur and why? Why does the rate of rise decrease leading up to the peak? Is the decrease after the peak faster or slower than the increase? What does this graph tell you about the drainage situation at this location?
 
 .. note::
-    If your subscription also includes the Scenario Archive, you can add a WMS layer of the water depth, and use the Temporal Controller to navigate through its time steps. This will give you additional insight in the progression of the flood through time. See the `Lizard documentation<https://docs.lizard.net/d_qgisplugin.html>`_ for more information.
+    If your subscription also includes the Scenario Archive, you can add a WMS layer of the water depth, and use the Temporal Controller to navigate through its time steps. This will give you additional insight in the progression of the flood through time. See the `Lizard documentation <https://docs.lizard.net/d_qgisplugin.html>`_ for more information.
 
 
 .. _tut6_why:
@@ -399,7 +399,7 @@ Quantification of the flood volume
 
 Now that we know *where* additional storage or buffer capacity would be helpful, we need to estimate how much storage is needed, so that we can use the correct dimensions in the design of our measure.
 
-.. _tut6_calc_flood_volume
+.. _tut6_calc_flood_volume:
 
 Calculating the flood volume
 ############################

source/h_subgrid.rst

@@ -48,6 +48,8 @@ The high resolution subgrid data is compressed in tables that allow fast access
 
 This relation is specific for each cell, node or, in case of cross-sectional area, flowline. When the cell is partially wet, the relation between water level and the other variables is non-lineair. The subgrid tables describe this non-linear relation using entries that contain a water level and e.g. (for volumes) the total water volume in the cell at that water level. Once the cell is completely wet, all relations become linear again (e.g. one cm rise in water level will always yield the same rise in volume), so the last entry in the subgrid tables is the highest point in the cell or cross-section.
 
+.. _subgrid_table_settings:
+
 Subgrid table settings
 ^^^^^^^^^^^^^^^^^^^^^^
 

source/i_running_a_simulation.rst

@@ -97,7 +97,7 @@ Boundary conditions
 
 .. Note:: You can only replace *all* boundary conditions. For example, if your model contains two 1D boundary conditions and five 2D boundary condition, the CSV file for the 1D boundary conditions should contain time series for both of the two 1D boundary conditions and the CSV file for the 2D boundary conditions should contain time series for all five 2D boundary conditions. The simulation wizard will merge them into a single JSON file that is sent to the API
 
-_boundary_conditions_csv_file_format:
+.. _boundary_conditions_csv_file_format:
 
 Boundary conditions CSV file format
 -----------------------------------
@@ -281,6 +281,7 @@ Generating a CSV file for 1D laterals
 - Click 'Ok' to save the file
 - You can now select the CSV file under the option "Upload file(s)" when adding scenario information. The time units in the spatialite (and therefore in the exported CSV) are minutes.
 
+.. _laterals_2d_csv_format_requirements:
 
 2D laterals file format
 -----------------------