Minor fixes in CDL Language Preliminaries (#2195)

Working through this section to learn more, I came across a few places
that might benefit from very minor improvements. Thanks!

- 24:59:59 is just wishful thinking :)
- remove duplicated paragraph
- add tip about made-up annotations in example
- clarify ref to prev model
- make comma spacing consistent

---------

Co-authored-by: René Jeglinsky <rene.jeglinsky@sap.com>

Author: qmacro

cds/cdl.md

@@ -41,7 +41,7 @@ The *Conceptual Definition Language (CDL)* is a human-readable language for defi
 
 ```cds
 namespace capire.bookshop;
-using { managed, cuid } from `@sap/cds/common`;
+using { managed, cuid } from '@sap/cds/common';
 aspect primary : managed, cuid {}
 
 entity Books : primary {
@@ -85,7 +85,7 @@ The following literals can be used in CDL (mostly as in JavaScript, Java, and SQ
 <!-- 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
+11 , 2.4 , 1e3 , 1.23e-11  // for numbers
 'A string''s literal'      // for strings
 `A string\n paragraph`     // for strings with escape sequences
 { foo:'boo', bar:'car' }   // for records
@@ -130,6 +130,10 @@ entity DocumentedEntity {
 }
 ```
 
+::: tip
+These annotations are illustrative only and are not defined nor have any meaning beyond this example.
+:::
+
 Within those strings, escape sequences from JavaScript, such as `\t` or `\u0020`, are supported. Line endings are normalized. If you don't want a line ending at that position, end a line with a backslash (`\`). For string literals inside triple backticks, indentation is stripped and tagging is possible.
 
 
@@ -238,7 +242,7 @@ context scoped {
 
 You can define types and entities with other definitions' names as prefixes:
 
-```cds
+```cds [prefixes.cds]
 namespace foo.bar;
 entity Foo {}           //> foo.bar.Foo
 entity Foo.Bar {}       //> foo.bar.Foo.Bar
@@ -248,7 +252,7 @@ type Foo.Bar.Car {}     //> foo.bar.Foo.Bar.Car
 
 #### Fully Qualified Names
 
-A model ultimately is a collection of definitions with unique, fully qualified names. For example, the second model above would compile to this [CSN](./csn):
+A model ultimately is a collection of definitions with unique, fully qualified names. For example, the model in `contexts.cds` would compile to the following [CSN](./csn):
 
 ::: code-group
 

cds/types.md

@@ -36,7 +36,7 @@ These types are used to define the structure of entities and services, and are m
 | `Decimal` (`prec`, `scale`) | A *decfloat* type is used if arguments are omitted | _DECIMAL_  |
 | `Double` | Floating point with binary mantissa | _DOUBLE_  |
 | `Date` | e.g. `2022-12-31` | _DATE_  |
-| `Time` | e.g. `24:59:59` | _TIME_  |
+| `Time` | e.g. `23:59:59` | _TIME_  |
 | `DateTime` | _sec_ precision | _TIMESTAMP_  |
 | `Timestamp` | _µs_ precision, with up to 7 fractional digits |  _TIMESTAMP_  |
 | `String` (`length`) | Default *length*: 255; on HANA: 5000 <sup>(4)(5)</sup> | _NVARCHAR_  |
@@ -46,8 +46,6 @@ These types are used to define the structure of entities and services, and are m
 | `Map` | Mapped to *NCLOB* for HANA. | *JSON* type |
 | `Vector` (`dimension `) | Requires SAP HANA Cloud QRC 1/2024, or later |  _REAL_VECTOR_  |
 
-These types are used to define the structure of entities and services, and are mapped to respective database types when the model is deployed.
-
 > <sup>(1)</sup> Concrete mappings to specific databases may differ.
 >
 > <sup>(2)</sup> See also [Best Practices](../guides/domain-modeling#don-t-interpret-uuids).