capire
diff --git a/‎.vitepress/config.js‎
Lines changed: 1 addition & 1 deletion b/‎.vitepress/config.js‎
Lines changed: 1 addition & 1 deletion
diff --git a/‎about/index.md‎
Lines changed: 8 additions & 3 deletions b/‎about/index.md‎
Lines changed: 8 additions & 3 deletions
diff --git a/‎cds/cdl.md‎
Lines changed: 1 addition & 2 deletions b/‎cds/cdl.md‎
Lines changed: 1 addition & 2 deletions
diff --git a/‎guides/providing-services.md‎
Lines changed: 2 additions & 2 deletions b/‎guides/providing-services.md‎
Lines changed: 2 additions & 2 deletions
@@ -106,7 +106,7 @@ config.rewrites = rewrites
 // Add custom capire info to the theme config
 config.themeConfig.capire = {
   versions: {
-    java_services: '4.3.0',
+    java_services: '4.3.1',
     java_cds4j: '4.3.0'
   },
   gotoLinks: []
 
@@ -378,11 +378,16 @@ Keeping pace with a rapidly changing world of volatile cloud technologies and pl
 ## What about AI? <UnderConstruction/>
 
 - AI provides tremendous boosts to productivity → for example:
-  - **Coding Assists** → for example, by [Copilot](https://en.wikipedia.org/wiki/Microsoft_Copilot) in `.cds`, `.js`, even `.md` sources
+  - **Coding Assists** → for example, by [GitHub Copilot](https://github.com/features/copilot) in `.cds`, `.js`, even `.md` sources
   - **Code Analysis** → detecting [bad practices](bad-practices) → guiding to [best practices](best-practices)
   - **Code Generation** → for example, for tests, test data, ...
   - **Project Scaffolding** → for quick head starts
-  - **Search & Learning Assists** → like Maui, ...
+  - **Search & Learning Assists** → like SAP Joule, ...
 - But this doesn't replace the need for **Human Intelligence**!
   - There's a different between a GPT-generated one-off thesis and long-lived enterprise software, which needs to adapt and scale to new requirements.
-- **CAP itself** is a major contribution to AI → its simple, clear concepts, uniform ways to implement and consume services, capire, its openness and visibility in the public world, ...
+
+By **embracing and advocating standard tooling** like VS Code and GitHub Actions, CAP ensures its projects are day-one beneficiaries of new AI features rolled out there.
+
+**CAP itself** is a major contribution to AI → its simple, clear concepts, uniform ways to implement and consume services make it easier for AIs and humans alike to reason about the system.
+
+Its openness and public visibility helped influence the very first AI models — even the original ChatGPT knew some CAP, and its baked-in knowledge of it has since improved dramatically.
@@ -422,7 +422,6 @@ definitions using the `projection on` syntax.
 You can use nested projections or aliases as known from entity projections.
 Only the effective signature of the projection is relevant.
 
-<!-- cds-mode: upcoming -->
 ```cds
 type CustomerData : projection on Customer {
   name.firstName, // select from structures
@@ -479,7 +478,7 @@ entity Bar {
 
 An element definition can be prefixed with modifier keyword `virtual`. This keyword indicates that this element isn't added to persistent artifacts, that is, tables or views in SQL databases. Virtual elements are part of OData metadata.
 
-By default, virtual elements are annotated with `@Core.Computed: true`, not writable for the client and will be [silently ignored](../guides/providing-services#readonly). This means also, that they are not accessible in custom event handlers. If you want to make virtual elements writable for the client, you explicitly need to annotate these elements with `@Core.Computed: false`. Still those elements are not persisted and therefore, for example, not sortable or filterable.
+By default, virtual elements are annotated with `@Core.Computed: true`, not writable for the client and will be [silently ignored](../guides/providing-services#readonly). This means also, that they are not accessible in custom event handlers. If you want to make virtual elements writable for the client, you explicitly need to annotate these elements with `@Core.Computed: false`. Still those elements are not persisted and therefore, for example, not sortable or filterable. Further, during read requests, you need to provide values for all virtual elements. You can do this by using post-processing in an `after` handler.
 
 ```cds
 entity Employees {
 
@@ -1378,13 +1378,13 @@ Content-Type: image/png
 
 One option is to delete the complete entity, including all media data:
 
-```cds
+```http
 DELETE ../Books(201)
 ```
 
 Alternatively, you can delete a media data element individually:
 
-```cds
+```http
 DELETE ../Books(201)/image
 ```