chore: Update generated docs

docs/includes/generated_docs/backends.md

@@ -30,15 +30,15 @@ time. For instance, students are often registered with a practice at home and a
 practice at university.
 
 !!! warning
-    Refer to the [discussion of selecting populations for studies](../../explanation/selecting-populations-for-study.md).
+    Refer to the [discussion of selecting populations for studies](../explanation/selecting-populations-for-study.md).
 
 This backend implements the following table schemas:
 
- * [core](../schemas/core/)
- * [raw.core](../schemas/raw.core/)
- * [tpp](../schemas/tpp/)
- * [raw.tpp](../schemas/raw.tpp/)
- * [smoketest](../schemas/smoketest/)
+ * [core](schemas/core.md)
+ * [raw.core](schemas/raw.core.md)
+ * [tpp](schemas/tpp.md)
+ * [raw.tpp](schemas/raw.tpp.md)
+ * [smoketest](schemas/smoketest.md)
 
 ## EMIS
 <small class="subtitle">
@@ -60,8 +60,8 @@ from other sources.
 
 This backend implements the following table schemas:
 
- * [core](../schemas/core/)
- * [raw.core](../schemas/raw.core/)
- * [raw.emis](../schemas/raw.emis/)
- * [emis](../schemas/emis/)
- * [smoketest](../schemas/smoketest/)
+ * [core](schemas/core.md)
+ * [raw.core](schemas/raw.core.md)
+ * [raw.emis](schemas/raw.emis.md)
+ * [emis](schemas/emis.md)
+ * [smoketest](schemas/smoketest.md)

docs/includes/generated_docs/language__dataset.md

@@ -54,7 +54,7 @@ An ehrQL query that returns one row per patient.
 Using `.add_column` is equivalent to `=` for adding a single column
 but can also be used to add multiple columns, for example by iterating
 over a dictionary. For more details see the guide on
-"[How to assign multiple columns to a dataset programmatically](/how-to/assign-multiple-columns)".
+"[How to assign multiple columns to a dataset programmatically](../how-to/assign-multiple-columns.md)".
 </div>
 
 <div class="attr-heading" id="Dataset.configure_dummy_data">

docs/includes/generated_docs/schemas/core.md

@@ -98,7 +98,7 @@ registered at the same practice for the duration of the study period.
 
 Examples of using ehrQL to calculation such periods can be found in the documentation
 on how to
-[use ehrQL to answer specifc questions](../../../how-to/examples#excluding-medications-for-patients-who-have-transferred-between-practices).
+[use ehrQL to answer specific questions](../../how-to/examples.md#excluding-medications-for-patients-who-have-transferred-between-practices).
 <div markdown="block" class="definition-list-wrapper">
   <div class="title">Columns</div>
   <dl markdown="block">
@@ -155,7 +155,7 @@ The `ehrql.tables.raw.ons_deaths` table contains all registered deaths.
 
 !!! tip
     If you need to query for place of death, please note that
-    this is only available in the tpp backend"
+    this is only available in the `tpp` backend
 <div markdown="block" class="definition-list-wrapper">
   <div class="title">Columns</div>
   <dl markdown="block">
@@ -402,7 +402,7 @@ based on these MCCDs.
 There is generally a lag between the death being recorded in ONS data and it
 appearing in the primary care record, but the coverage or recorded death is almost
 complete and the date of death is usually reliable when it appears. There is
-also a lag in ONS death recording (see [`ons_deaths`](/reference/schemas/core/#ons_deaths) below
+also a lag in ONS death recording (see [`ons_deaths`](#ons_deaths) below
 for more detail). You can find out more about the accuracy of date of death
 recording in primary care in:
 

docs/includes/generated_docs/schemas/emis.md

@@ -99,7 +99,7 @@ registered at the same practice for the duration of the study period.
 
 Examples of using ehrQL to calculation such periods can be found in the documentation
 on how to
-[use ehrQL to answer specifc questions](../../../how-to/examples#excluding-medications-for-patients-who-have-transferred-between-practices).
+[use ehrQL to answer specific questions](../../how-to/examples.md#excluding-medications-for-patients-who-have-transferred-between-practices).
 <div markdown="block" class="definition-list-wrapper">
   <div class="title">Columns</div>
   <dl markdown="block">
@@ -156,7 +156,7 @@ The `ehrql.tables.raw.ons_deaths` table contains all registered deaths.
 
 !!! tip
     If you need to query for place of death, please note that
-    this is only available in the tpp backend"
+    this is only available in the `tpp` backend
 <div markdown="block" class="definition-list-wrapper">
   <div class="title">Columns</div>
   <dl markdown="block">

docs/includes/generated_docs/schemas/tpp.md

@@ -1358,7 +1358,7 @@ registered at the same practice for the duration of the study period.
 
 Examples of using ehrQL to calculation such periods can be found in the documentation
 on how to
-[use ehrQL to answer specifc questions](../../../how-to/examples#excluding-medications-for-patients-who-have-transferred-between-practices).
+[use ehrQL to answer specific questions](../../how-to/examples.md#excluding-medications-for-patients-who-have-transferred-between-practices).
 <div markdown="block" class="definition-list-wrapper">
   <div class="title">Columns</div>
   <dl markdown="block">
@@ -2205,7 +2205,7 @@ based on these MCCDs.
 There is generally a lag between the death being recorded in ONS data and it
 appearing in the primary care record, but the coverage or recorded death is almost
 complete and the date of death is usually reliable when it appears. There is
-also a lag in ONS death recording (see [`ons_deaths`](/reference/schemas/core/#ons_deaths) below
+also a lag in ONS death recording (see [`ons_deaths`](#ons_deaths) below
 for more detail). You can find out more about the accuracy of date of death
 recording in primary care in:
 
@@ -2296,7 +2296,7 @@ return (date - patients.date_of_birth).years
 
 Each record corresponds to a patient's registration with a practice.
 
-See the [TPP backend information](../../backends.md#patients-included-in-the-tpp-backend)
+See the [TPP backend information](../backends.md#patients-included-in-the-tpp-backend)
 for details of which patients are included.
 <div markdown="block" class="definition-list-wrapper">
   <div class="title">Columns</div>