fix: Fix cds-snippet-checker errors (#1430)

Fixes issues introduced in 4534536 and
dc5800c

---------

Co-authored-by: Christian Georgi <christian.georgi@sap.com>

Author: bugwelle

cds/cdl.md

@@ -43,9 +43,9 @@ The *CDS Definition Language (CDL)* is a human-readable language for defining CD
 *Keywords* in CDL are used to prelude statements, such as imports and namespace directives as well as entity and type declarations. *Identifiers* are used to refer to definitions.
 
 ```cds
+namespace capire.bookshop;
 using { managed } from `@sap/cds/common`;
 aspect entity : managed { key ID: Integer }
-namespace capire.bookshop;
 
 entity Books : entity {
   title  : String;
@@ -93,6 +93,7 @@ Delimited identifiers in general, but in articular non-ansi characters, or keywo
 
 The following literals can be used in CDL (mostly as in JavaScript, Java, and SQL):
 
+<!-- cds-mode: ignore; values only, no valid CDS file -->
 ```cds
 true , false , null        // as in all common languages
 11 , 2.4 , 1e3, 1.23e-11   // for numbers
@@ -105,8 +106,9 @@ true , false , null        // as in all common languages
 
 #### Date & Time Literals
 
-In addition type-keyword-prefixed strings can be used for date & time literals:
+In addition, type-keyword-prefixed strings can be used for date & time literals:
 
+<!-- cds-mode: ignore; values only, no valid CDS file -->
 ```cds
 date'2016-11-24'
 time'16:11:32'

cds/compiler/hdbcds-to-hdbtable.md

@@ -120,7 +120,7 @@ In contrast to the `hdbtable` plugin, the `hdbcds` plugin is able to handle remo
 
 ## Multiline Doc Comments
 
-This is only relevant if you have switched on [Doc Comments](../../cds/cdl#doc-comments-%E2%80%94)
+This is only relevant if you have switched on [Doc Comments](../../cds/cdl#doc-comment)
 and if you have enabled translation of doc comments to the `COMMENT` feature in the database.
 
 Doc comments can span across multiple lines:

guides/domain-modeling.md

@@ -253,7 +253,7 @@ entity name {
 }
 ```
 
-[Learn more about entity definitions](../cds/cdl.md#entity-and-type-definitions){.learn-more}
+[Learn more about entity definitions](../cds/cdl.md#views-projections){.learn-more}
 
 
 
@@ -267,7 +267,7 @@ entity ProjectedEntity as select from BaseEntity {
 };
 ```
 
-[Learn more about views and projections](../cds/cdl.md#views-and-projections){.learn-more}
+[Learn more about views and projections](../cds/cdl.md#views-projections){.learn-more}
 
 
 

guides/providing-services.md

@@ -903,12 +903,14 @@ entity Foo {
 
 By default, specified `[min,max]` ranges are interpreted as closed intervals, that means, the performed checks are `min ≤ input ≤ max`. You can also specify open intervals by wrapping the *min* and/or *max* values into parenthesis like that:
 
+<!-- cds-mode: ignore; duplicate annotations -->
 ```cds
 @assert.range: [(0),100]    // 0 < input ≤ 100
 @assert.range: [0,(100)]    // 0 ≤ input < 100
 @assert.range: [(0),(100)]  // 0 < input < 100
 ```
 In addition, you can use an underscore `_` to represent *Infinity* like that:
+<!-- cds-mode: ignore; duplicate annotations -->
 ```cds
 @assert.range: [(0),_]  // positive numbers only, _ means +Infinity here
 @assert.range: [_,(0)]  // negative number only, _ means -Infinity here

java/working-with-cql/query-execution.md

@@ -403,7 +403,7 @@ The parameter `mode` allows to specify whether an `EXCLUSIVE` or a `SHARED` lock
 
 ## Runtime Views { #runtimeviews}
 
-The CDS compiler generates [SQL DDL](../../guides/databases?impl-variant=java#generating-sql-ddl) statements based on your CDS model, which include SQL views for all CDS [views and projections](../../cds/cdl#views-and-projections). This means adding or changing CDS views requires a deployment of the database schema changes.
+The CDS compiler generates [SQL DDL](../../guides/databases?impl-variant=java#generating-sql-ddl) statements based on your CDS model, which include SQL views for all CDS [views and projections](../../cds/cdl#views-projections). This means adding or changing CDS views requires a deployment of the database schema changes.
 
 To avoid schema updates due to adding or updating CDS views, annotate them with [@cds.persistence.skip](../../guides/databases#cds-persistence-skip). In this case the CDS compiler won't generate corresponding static database views. Instead, the CDS views are dynamically resolved by the CAP Java runtime.