doc: Fix broken headings with shortcodes

TheThingsIndustries · Dec 29, 2020 · 87c19bc · 87c19bc
1 parent 6dc923b
commit 87c19bc
Show file tree

Hide file tree

Showing 5 changed files with 5 additions and 5 deletions.
diff --git a/doc/content/gateways/semtech-udp-packet-forwarder/_index.md b/doc/content/gateways/semtech-udp-packet-forwarder/_index.md
@@ -22,7 +22,7 @@ An example `global_conf.json` is available in the [{{% udp-pf %}} Github reposit
 
 {{< tabs/tab "Console" >}}
 
-## Download Configuration in the Console {{< new-in-version "3.10" >}}
+## Download Configuration in the Console {{< new-in-version "3.10" >}} {#download-configuration-in-the-console}
 
 To download a `global_conf.json` file for your gateway, open the Gateway overview page in the console. Click the **Download global_conf.json** button to download the file.
 

diff --git a/doc/content/getting-started/aws/ecs/deployment/_index.md b/doc/content/getting-started/aws/ecs/deployment/_index.md
@@ -88,7 +88,7 @@ It is recommended to have a **Multi-AZ** cluster with automatic failover, in whi
 
 If you are migrating your database from a previous deployment, or if you are upgrading your database, you can fill the name of the database **Snapshot** that should be restored.
 
-## TimescaleDB (optional) {{< new-in-version "3.10" >}}
+## TimescaleDB (optional) {{< new-in-version "3.10" >}} {#timescaledb-optional}
 
 The template `2-5-db-timescale` is an optional template that creates an EC2 instance that runs [TimescaleDB](https://www.timescale.com/), which is used by the Storage Integration of the Application Server. 
 

diff --git a/doc/content/getting-started/migrating/import-devices.md b/doc/content/getting-started/migrating/import-devices.md
@@ -12,7 +12,7 @@ To import devices, use the `devices.json` file you created in the previous step.
 
 {{< tabs/tab "Console" >}}
 
-### Import devices via the Console {{< new-in-version "3.9.3" >}}
+### Import devices via the Console {{< new-in-version "3.9.3" >}} {#import-devices-via-the-console}
 
 Open the application you created and click the button **Import end devices**
 

diff --git a/doc/content/integrations/aws-iot/default/architecture.md b/doc/content/integrations/aws-iot/default/architecture.md
@@ -20,7 +20,7 @@ The key resources deployed in your AWS account are:
 
 This is a serverless deployment: there are no compute resources being deployed. AWS only charges for usage, which is driven by traffic. The only continuous charges are by IoT Core connectivity from {{% tts %}} to your AWS account. All permissions are the minimum permissions for the integration to function.
 
-## End-to-End Encryption {{< new-in-version "3.10.0" >}}
+## End-to-End Encryption {{< new-in-version "3.10.0" >}} {#end-to-end-encryption}
 
 This integration supports true LoRaWAN end-to-end encryption: the application payload is encrypted on the end device with the LoRaWAN AppSKey, and decrypted in your AWS Account. The underlying network infrastructure passes your application payload in the encrypted form - it cannot see your data.
 

diff --git a/doc/content/reference/configuration/identity-server.md b/doc/content/reference/configuration/identity-server.md
@@ -136,7 +136,7 @@ By default users can create applications, gateways, organizations and OAuth clie
 - `is.user-rights.create-gateways`: Allow non-admin users to create gateways in their user account
 - `is.user-rights.create-organizations`: Allow non-admin users to create organizations in their user account
 
-## Gateway Secrets Encryption Options {{< new-in-version "3.10" >}}
+## Gateway Secrets Encryption Options {{< new-in-version "3.10" >}} {#gateway-secrets-encryption-options}
 
 - `is.gateways.encryption-key-id`: ID of the key used to encrypt gateway secrets at rest.