Fix some feature anchors

helgoboss · Nov 27, 2024 · 987e458 · 987e458
1 parent 944f7af
commit 987e458
Show file tree

Hide file tree

Showing 6 changed files with 6 additions and 6 deletions.
diff --git a/doc/playtime/modules/ROOT/pages/advanced-usage-scenarios/generate-matrix.adoc b/doc/playtime/modules/ROOT/pages/advanced-usage-scenarios/generate-matrix.adoc
@@ -1,6 +1,6 @@
-[[feature-import-export-lua]]
 = Generate a matrix using code
 
+[[feature-import-export-lua]]
 Just as it is possible to xref:advanced-usage-scenarios/control-with-items.adoc#assign-midi-triggers-automatically[generate ReaLearn mappings via Luau], you can also generate a Playtime xref:key-concepts.adoc#matrix[] via Luau.
 
 .This guide is a work in progress

diff --git a/doc/playtime/modules/ROOT/pages/advanced-usage-scenarios/meta-clips.adoc b/doc/playtime/modules/ROOT/pages/advanced-usage-scenarios/meta-clips.adoc
@@ -1,8 +1,8 @@
-[[feature-meta-clips]]
 = Meta clips
 
 We can take the previous scenario xref:advanced-usage-scenarios/control-with-items.adoc[] a step further!
 
+[[feature-meta-clips]]
 == The idea
 
 If we can control Playtime with MIDI items, shouldn't it be possible to control it with MIDI xref:key-concepts.adoc#clip[_clips_] as well? The answer is yes! I call such clips _meta clips_. *Playtime can basically play itself!*

diff --git a/doc/playtime/modules/ROOT/pages/advanced-usage-scenarios/multiple-instances.adoc b/doc/playtime/modules/ROOT/pages/advanced-usage-scenarios/multiple-instances.adoc
@@ -1,6 +1,6 @@
-[[feature-multiple-instances]]
 = Multiple instances
 
+[[feature-multiple-instances]]
 Because Helgobox is implemented as an xref:helgobox::plug-in.adoc[instrument plug-in], you can add multiple xref:helgobox::key-concepts.adoc#instance[instances] of it. That also means you can have multiple xref:key-concepts.adoc#matrix[Playtime matrices] in the same project.
 
 == How to do it

diff --git a/doc/playtime/modules/ROOT/pages/realearn-targets.adoc b/doc/playtime/modules/ROOT/pages/realearn-targets.adoc
@@ -1,6 +1,6 @@
-[[feature-realearn]]
 = ReaLearn targets
 
+[[feature-realearn]]
 xref:realearn::introduction.adoc[ReaLearn] offers a bunch of xref:realearn::key-concepts.adoc#target[targets] specific to Playtime. Most of them even support xref:realearn::key-concepts.adoc#feedback[], to power LEDs or displays. That gives you the power to create highly customized controller integrations for Playtime!
 
 To get an impression of that power, you just need to look at Playtime's xref:usage/grid-controllers.adoc[support for grid controllers]. This support is not hard-coded into Playtime. It is implemented solely in the form of xref:realearn::further-concepts/compartment.adoc#compartment-preset[ReaLearn compartment presets].

diff --git a/doc/playtime/modules/ROOT/pages/usage/grid-controllers.adoc b/doc/playtime/modules/ROOT/pages/usage/grid-controllers.adoc
@@ -1,6 +1,6 @@
-[[feature-grid]]
 = Use grid controllers
 
+[[feature-grid]]
 .Grid controllers are optional!
 TIP: You don't need a xref:key-concepts.adoc#grid-controller[] to use Playtime! However, using one adds a tactile dimension to the clip-launching experience, making Playtime feel more like a distinct musical instrument. It’s a fun way to enhance interaction and creativity.
 

diff --git a/doc/realearn/modules/ROOT/pages/user-interface/controller-dialog.adoc b/doc/realearn/modules/ROOT/pages/user-interface/controller-dialog.adoc
@@ -1,6 +1,6 @@
-[[feature-realearn-customize]]
 = Controller dialog
 
+[[feature-realearn-customize]]
 include::partial$available-in-app.adoc[]
 
 This dialog appears when clicking a controller in xref:user-interface/settings-dialog.adoc#controllers[]. It allows you to configure a xref:key-concepts.adoc#managed-controller[] and define how it should be used.