apply rumdl auto-fixes

Author: rpietzsch

docs/automate/cmemc-command-line-interface/command-reference/admin/workspace/index.md

@@ -67,5 +67,5 @@ cmemc admin workspace reload
 Request a thread dump for all live threads.
 
 ```shell-session title="Usage"
-$ cmemc admin workspace thread-dump
+cmemc admin workspace thread-dump
 ```

docs/automate/cmemc-command-line-interface/command-reference/query/index.md

@@ -194,7 +194,7 @@ With this command, you can cancel a running query. Depending on the backend trip
 Explain queries by showing their logical execution plan.
 
 ```shell-session title="Usage"
-$ cmemc query explain [OPTIONS] QUERIES...
+cmemc query explain [OPTIONS] QUERIES...
 ```
 
 
@@ -227,7 +227,7 @@ This helps understand query performance and identify optimization opportunities.
 Create a new query in a query catalog.
 
 ```shell-session title="Usage"
-$ cmemc query create [OPTIONS] QUERY_FILE
+cmemc query create [OPTIONS] QUERY_FILE
 ```
 
 
@@ -238,7 +238,7 @@ Creates a new query in a query catalog from a SPARQL query file.
 The query type (SELECT, CONSTRUCT, UPDATE, etc.) is automatically detected from the query text.
 
 ```shell-session title="Example"
-$ cmemc query create my-query.sparql $ cmemc query create my-query.sparql --id :customName
+cmemc query create my-query.sparql $ cmemc query create my-query.sparql --id :customName
 ```
 
 
@@ -263,7 +263,7 @@ $ cmemc query create my-query.sparql $ cmemc query create my-query.sparql --id :
 Update an existing query in a query catalog.
 
 ```shell-session title="Usage"
-$ cmemc query update [OPTIONS] QUERY_ID
+cmemc query update [OPTIONS] QUERY_ID
 ```
 
 
@@ -290,7 +290,7 @@ The `QUERY_ID` can be either a short URI (e.g., :myQuery) or a full URI.
 Delete queries from a query catalog.
 
 ```shell-session title="Usage"
-$ cmemc query delete [OPTIONS] [QUERY_IDS]...
+cmemc query delete [OPTIONS] [QUERY_IDS]...
 ```
 
 

docs/build/integrations/index.md

@@ -56,6 +56,7 @@ to interact with any [Azure AI Foundry provided Large Language Models](https://a
     [Databricks](http://databricks.com/) can be accessed with the [Remote SQL endpoint](../../build/reference/dataset/Jdbc.md) dataset and a
 [Custom JDBC driver](https://github.com/databricks/databricks-jdbc).
 Please have a look at
+
 [Setup and use of JDBC Drivers](../../deploy-and-configure/configuration/dataintegration/jdbc/index.md).
 
 
@@ -335,6 +336,7 @@ execute a [SOQL query (Salesforce)](../../build/reference/customtask/cmem_plugin
     SQLite can be accessed with the [Remote SQL endpoint](../../build/reference/dataset/Jdbc.md) dataset and a
 [Custom JDBC driver](https://central.sonatype.com/artifact/org.xerial/sqlite-jdbc).
 Please have a look at
+
 [Setup and use of JDBC Drivers](../../deploy-and-configure/configuration/dataintegration/jdbc/index.md).
 
 
@@ -365,6 +367,7 @@ Tentris can be used as the integrated Quad Store as well (beta).
     [Trino](https://github.com/trinodb/trino) can be access with the [Remote SQL endpoint](../../build/reference/dataset/Jdbc.md) dataset and a
 [Custom JDBC driver](https://trino.io/docs/current/client/jdbc.html).
 Please have a look at
+
 [Setup and use of JDBC Drivers](../../deploy-and-configure/configuration/dataintegration/jdbc/index.md).
 
 

docs/build/snowflake-tutorial/index.md

@@ -22,10 +22,10 @@ This integration enables organizations to make informed decisions, improve their
 
 This tutorial contains the following step-by-step instructions to connect the Snowflake data-warehouse with eccenca corporate memory:
 
--   [1. Create a database in Snowflake](#1-create-a-database-in-snowflake)
--   [2. Create a project in eccenca Corporate Memory](#2-create-a-project-in-eccenca-corporate-memory)
--   [3. Create a transformation to build mapping rules](#3-create-a-transformation-to-build-mapping-rules)
--   [4. Create a knowledge graph](#4-create-a-knowledge-graph)
+- [1. Create a database in Snowflake](#1-create-a-database-in-snowflake)
+- [2. Create a project in eccenca Corporate Memory](#2-create-a-project-in-eccenca-corporate-memory)
+- [3. Create a transformation to build mapping rules](#3-create-a-transformation-to-build-mapping-rules)
+- [4. Create a knowledge graph](#4-create-a-knowledge-graph)
 
 ## Sample material
 
@@ -1119,13 +1119,13 @@ Here you can populate some test data with the following SQL query:
 
     ![image](snowflake-create.png){ class="bordered" }
 
--   Click on **Snowflake SQL endpoint**, then click on **Add**.
+- Click on **Snowflake SQL endpoint**, then click on **Add**.
 
     ![image](snowflake-jdbc.png){ class="bordered" }
 
--   Type the name **Product table (JDBC)** in the label field.
+- Type the name **Product table (JDBC)** in the label field.
 
--   In the **CONNECTION** section populate the required details.
+- In the **CONNECTION** section populate the required details.
 
     ![image](snowflake-connection.png){ class="bordered" }
 
@@ -1141,23 +1141,23 @@ Here you can populate some test data with the following SQL query:
 
     -   Select your **Schema**, `products_vocabulary` in this case
 
--   In the **READ** section specify **Source query** as
+- In the **READ** section specify **Source query** as
 
     ```sparql
     SELECT * from product
     ```
 
     ![image](snowflake-query-source.png){ class="bordered" }
 
--   Select the **Query strategy** as **Execute the given source query. No paging or virtual query**.
+- Select the **Query strategy** as **Execute the given source query. No paging or virtual query**.
 
     ![image](snowflake-query-strategy.png){ class="bordered" }
 
 - Select the **Write strategy** as **An exception will be thrown, if the table already exists.**
 
     ![image](snowflake-write-stategy.png){ class="bordered" }
 
--   Then click on **Create**.
+- Then click on **Create**.
 
 !!! success "Step Result"
 

docs/deploy-and-configure/configuration/label-resolution-and-full-text-search/index.md

@@ -9,9 +9,9 @@ This resolution and, by extension, the full text search is configurable for diff
 
 eccenca Explore backend (DataPlatform) offers three configuration options:
 
--   `labelProperties` (line 2) 
--   `languagePreferences` (line 5) and 
--   `languagePreferencesAnyLangFallback` (line 8).
+- `labelProperties` (line 2) 
+- `languagePreferences` (line 5) and 
+- `languagePreferencesAnyLangFallback` (line 8).
 
 ``` yaml linenums="1"
 proxy:
@@ -28,8 +28,8 @@ These properties define not only which properties and languages should be consid
 
 The retrieval process can be simplified to the following procedure:
 
--   First, when determining the label for a resource, the language is evaluated, then the property is considered.
--   Consequently, for a resource in the default case:
+- First, when determining the label for a resource, the language is evaluated, then the property is considered.
+- Consequently, for a resource in the default case:
     1. An english value for `rdfs:label` is searched.
     2. A literal of the property `rdfs:label` without a language tag is searched (which is why there is an entry `""`).
     3. An english value of `skos:prefLabel` is searched.
@@ -50,12 +50,12 @@ How labels are resolved is best explained using these default settings and some
 :Resource4 rdfs:label "Another Label for Hanover"@en
 ```
 
--   For `:Resource1` the label will be `Leipzig` as the english `rdfs:label` will be retrieved.
--   For `:Resource2` the label cannot be retrieved from the Knowledge Graph since no known property is used. Hence the fallback.
--   For `:Resource3` the label will be retrieved as `Stuttgart`, if the `languagePreferencesAnyLangFallback` is `true`.
-    -   While there is a well-known property used, none of the used languages match. Using the fallback, the alphabetically first match is retrieved in this case.
--   For `:Resource4` multiple label candidates could be determined.
-    -   In this case, `Another Label for Hanover` is retrieved as it is the first value in the alphanumerical comparison.
+- For `:Resource1` the label will be `Leipzig` as the english `rdfs:label` will be retrieved.
+- For `:Resource2` the label cannot be retrieved from the Knowledge Graph since no known property is used. Hence the fallback.
+- For `:Resource3` the label will be retrieved as `Stuttgart`, if the `languagePreferencesAnyLangFallback` is `true`.
+    - While there is a well-known property used, none of the used languages match. Using the fallback, the alphabetically first match is retrieved in this case.
+- For `:Resource4` multiple label candidates could be determined.
+    - In this case, `Another Label for Hanover` is retrieved as it is the first value in the alphanumerical comparison.
 
 ## Client API