fixed TOC (#150)

Author: nkaputnik

README.md

@@ -6,15 +6,19 @@ a [CDS plugin](https://cap.cloud.sap/docs/node.js/cds-plugins#cds-plugin-package
 
 > [!IMPORTANT]
 > This release establishes support for multi-tenant deployments using MTX and extensibility.
+> This release establishes support for multi-tenant deployments using MTX and extensibility.
 > 
 > To achieve this, the code was modified significantly. While we tested extensively, there still may be glitches or unexpected situations which we did not cover. So please **test this release extensively before applying it to productive** scenarios. Please also report any bugs or glitches, ideally by contributing a test-case for us to incorporate.
+> To achieve this, the code was modified significantly. While we tested extensively, there still may be glitches or unexpected situations which we did not cover. So please **test this release extensively before applying it to productive** scenarios. Please also report any bugs or glitches, ideally by contributing a test-case for us to incorporate.
 > 
 > See the changelog for a full list of changes
 
 > [!Warning]
 >
 > When using multi-tenancy with MTX, the generated facets and associations have to be created by the model provider of the MTX component. Therefore, the plugin also must be added to the `package.json` of the MTX sidecar. 
 >Although we tested this scenario extensively, there still might be cases where the automatic generation will not work as expected. If this happends in your scenario, we suggest using the `@changelog.disable_assoc` ([see here](#disable-association-to-changes-generation)) for all tracked entities and to add the association and facet manually to the service entity.
+> When using multi-tenancy with MTX, the generated facets and associations have to be created by the model provider of the MTX component. Therefore, the plugin also must be added to the `package.json` of the MTX sidecar. 
+>Although we tested this scenario extensively, there still might be cases where the automatic generation will not work as expected. If this happends in your scenario, we suggest using the `@changelog.disable_assoc` ([see here](#disable-association-to-changes-generation)) for all tracked entities and to add the association and facet manually to the service entity.
 
 
 ### Table of Contents
@@ -76,6 +80,7 @@ To enable change tracking, simply add this self-configuring plugin package to yo
 npm add @cap-js/change-tracking
 ```
 If you use multi-tenancy, please add the plugin also to the MTX poroject.
+If you use multi-tenancy, please add the plugin also to the MTX poroject.
 
 ### 3. Annotations
 
@@ -267,24 +272,6 @@ You can turn this behavior off globally by adding the following switch to the `p
 
 This section describes modelling cases for further reference, from simple to complex, including the following:
 
-- [Change Tracking Plugin for SAP Cloud Application Programming Model (CAP)](#change-tracking-plugin-for-sap-cloud-application-programming-model-cap)
-    - [Table of Contents](#table-of-contents)
-  - [Try it Locally](#try-it-locally)
-    - [1. Prerequisites](#1-prerequisites)
-    - [2. Setup](#2-setup)
-    - [3. Annotations](#3-annotations)
-    - [4. Testing](#4-testing)
-      - [Change History View](#change-history-view)
-  - [Detailed Explanation](#detailed-explanation)
-    - [Human-readable Types and Fields](#human-readable-types-and-fields)
-    - [Human-readable IDs](#human-readable-ids)
-    - [Human-readable Values](#human-readable-values)
-  - [Advanced Options](#advanced-options)
-    - [Altered table view](#altered-table-view)
-    - [Disable lazy loading](#disable-lazy-loading)
-    - [Disable UI Facet generation](#disable-ui-facet-generation)
-    - [Disable Association to Changes Generation](#disable-association-to-changes-generation)
-    - [Preserve change logs of deleted data](#preserve-change-logs-of-deleted-data)
   - [Examples](#examples)
     - [Specify Object ID](#specify-object-id)
       - [Use Case 1: Annotate single field/multiple fields of associated table(s) as the Object ID](#use-case-1-annotate-single-fieldmultiple-fields-of-associated-tables-as-the-object-id)