Fixing broken links

Altinn · Dec 16, 2024 · 2632ea5 · 2632ea5
1 parent b288960
commit 2632ea5
Show file tree

Hide file tree

Showing 5 changed files with 13 additions and 13 deletions.
diff --git a/content/altinn-studio/guides/development/options/sources/_index.en.md b/content/altinn-studio/guides/development/options/sources/_index.en.md
@@ -7,11 +7,11 @@ weight: 10
 When you set up an options-enabled component in Altinn Studio, it needs to be connected to a source of options. There are three different properties in the component configuration that can be used for this, depending on the use case:
 
 
-| Property    | Usage                                                                                                                            |
-|-------------|----------------------------------------------------------------------------------------------------------------------------------|
-| `options`   | [Static options defined per-component](./static/#in-component-configuration)                                                     |
-| `optionsId` | Either [code lists from json files](./static/#from-json-files), [dynamic code lists](./dynamic) or [shared code lists](./shared) |
-| `source`    | [Code lists from the data model](./from-data-model)                                                                              |
+| Property    | Usage                                                                                                                                      |
+|-------------|--------------------------------------------------------------------------------------------------------------------------------------------|
+| `options`   | [Static options defined per-component](./static/#in-component-configuration-options)                                                       |
+| `optionsId` | Either [code lists from json files](./static/#from-json-files-code-list), [dynamic code lists](./dynamic) or [shared code lists](./shared) |
+| `source`    | [Code lists from the data model](./from-data-model)                                                                                        |
 
 At least one such property has to be set in the component configuration. If multiple are set, the configuration precedence will be the opposite of the table above, so `source` will take precedence over `optionsId`, which will take precedence over `options`.
 

diff --git a/content/altinn-studio/guides/development/options/sources/_index.nb.md b/content/altinn-studio/guides/development/options/sources/_index.nb.md
@@ -8,11 +8,11 @@ Når du setter opp en komponent i Altinn Studio som skal ha svaralternativer, m
 svaralternativer. Det er tre forskjellige egenskaper i komponentkonfigurasjonen som kan brukes til dette,
 avhengig av bruksområdet:
 
-| Egenskap    | Bruksområde                                                                                                                                |
-|-------------|--------------------------------------------------------------------------------------------------------------------------------------------|
-| `options`   | [Statiske svaralternativer definert per komponent](./static/#i-komponentkonfigurasjonen)                                                   |
-| `optionsId` | Enten [statiske kodelister fra json-filer](./static/#fra-json-filer), [dynamiske kodelister](./dynamic) eller [delte kodelister](./shared) |
-| `source`    | [Kodelister fra datamodellen](./from-data-model)                                                                                           |
+| Egenskap    | Bruksområde                                                                                                                                          |
+|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `options`   | [Statiske svaralternativer definert per komponent](./static/#i-komponentkonfigurasjonen-svaralternativer)                                            |
+| `optionsId` | Enten [statiske kodelister fra json-filer](./static/#fra-json-filer-kodeliste), [dynamiske kodelister](./dynamic) eller [delte kodelister](./shared) |
+| `source`    | [Kodelister fra datamodellen](./from-data-model)                                                                                                     |
 
 Minst en slik egenskap må settes i komponentkonfigurasjonen. Hvis flere er satt, vil konfigurasjonsprioriteten være motsatt av tabellen ovenfor, slik at `source` vil ha forrang over `optionsId`, som vil ha forrang over `options`.
 

diff --git a/content/altinn-studio/guides/development/options/sources/static/_index.en.md b/content/altinn-studio/guides/development/options/sources/static/_index.en.md
@@ -12,7 +12,7 @@ For simpler use-cases, a static list of options or a simple code list is easy to
 These can either be set directly in the component configuration (in which case we call them options) or in a json file
 in the application repository (the simplest form for code lists). Which method to use depends on the need for reusability.
 If multiple components need to use the same set of options, it is recommended to
-use the [json file method](#from-json-files) and thus turn it into a code list.
+use the [json file method](#from-json-files-code-list) and thus turn it into a code list.
 
 Note that even though a static list of options can be completely static, it is also possible to make it (a bit more) dynamic
 by [filtering the options](../../functionality/filtering) using expressions. If you want even more flexibility,

diff --git a/content/altinn-studio/guides/development/options/sources/static/_index.nb.md b/content/altinn-studio/guides/development/options/sources/static/_index.nb.md
@@ -12,7 +12,7 @@ For enklere brukstilfeller er statiske svaralternativer og kodelister det lettes
 i komponentkonfigurasjonen (dette kaller vi ofte svaralternativer) eller i en json-fil i
 app-repositoriet (den enkleste formen for kodeliste). Hvilken metode som bør brukes avhenger av
 gjenbruksbehovet. Hvis flere komponenter skal bruke de samme svaralternativene, anbefales det å
-[putte kodelisten i en json-fil](#fra-json-filer) og dermed gjøre den om til en kodeliste.
+[putte kodelisten i en json-fil](#fra-json-filer-kodeliste) og dermed gjøre den om til en kodeliste.
 
 Legg merke til at selv om slike svaralternativer kan være helt statisk, er det også mulig å gjøre dem (litt mer) dynamiske
 ved å [filtrere svaralternativene](../../functionality/filtering) ved hjelp av et uttrykk. Ønsker du enda mer

diff --git a/...ent/altinn-studio/reference/ux/components/_common-props-content/optionsId.en.md b/...ent/altinn-studio/reference/ux/components/_common-props-content/optionsId.en.md
@@ -19,7 +19,7 @@ To add options from a code list, select "Kodeliste" and enter a code list ID.
 
 <br>
 
-If you wish to [secure dynamic code lists](/altinn-studio/guides/development/options/sources/dynamic/#secured-options), you can check this option:
+If you wish to [secure dynamic code lists](/altinn-studio/guides/development/options/sources/dynamic/#secured-code-lists), you can check this option:
 
 {{% image file="component-settings/secure.png" %}}
 <!-- end asd -->