add

Signed-off-by: A.Arnold <[email protected]>

Author: anarnold97

docs/topics/yaml-rule-structure-syntax.adoc

@@ -228,7 +228,8 @@ when:
 
 {ProductShortName} supports three types of conditions: `provider`, `and`, and `or`.
 
-==== Provider conditions
+[id="yaml-provider-conditions_{context}"]
+=== Provider conditions
 
 The Application Analyzer detects the programming languages, frameworks, and tools used to build an application, and it generates default rulesets for each supported provider using the Language Server Protocol (LSP) accordingly.
 Each supported provider has a ruleset defined by default and is run independently in a separate container.
@@ -273,7 +274,8 @@ a|
 * Node.js
 |===
 
-===== `builtin` provider
+[id="yaml-builtin-provider_{context}"]
+==== `builtin` provider
 
 `builtin` is an internal provider that can analyze various files and internal metadata generated by the engine.
 
@@ -350,7 +352,8 @@ when:
 ----
 <1> When more than one tag is given, a logical AND is implied.
 
-===== `java` provider
+[id="yaml-java-provider_{context}"]
+==== `java` provider
 
 The Language Server used by the Java provider is Eclipse’s JDT Language Server (JDTLS). Internally, the JDTLS uses the Eclipse Java Development Toolkit, which includes utilities for searching code in projects.
 
@@ -431,8 +434,8 @@ java.referenced:
   pattern: java.util.List
 ----
 
-=====
-====== `java` locations
+[id="yaml-java-locations_{context}"]
+===== `java` locations
 
 The Java provider allows scoping down the search to certain source code locations. You can scope down Java searches from any one of the following search locations: