From 1bd5ca04e37d139488296e0caa23326054c984b8 Mon Sep 17 00:00:00 2001 From: Martin De Corte Date: Fri, 13 Feb 2026 14:56:23 +0100 Subject: [PATCH] fixed text --- get-started/concepts.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/get-started/concepts.md b/get-started/concepts.md index d67205fcea..7bdce1e4b0 100644 --- a/get-started/concepts.md +++ b/get-started/concepts.md @@ -441,7 +441,7 @@ All data processed and served by CAP services is *passive*, and represented by * ### Extensible Data -Extensibility, in particular in a SaaS context, allows customers to tailor a SaaS application to their needs by adding extension fields. These fields are not known at design time but need to be served by your services, potentially through all interfaces. CAP's combination of dynamic querying and passive data this is intrinsically covered and extension fields look and feel no different than pre-defined fields. +Extensibility, in particular in a SaaS context, allows customers to tailor a SaaS application to their needs by adding extension fields. These fields are not known at design time but need to be served by your services, potentially through all interfaces. With CAP's combination of dynamic querying and passive data this is intrinsically covered and extension fields look and feel no different than pre-defined fields. For example, an extension like that can automatically be served by CAP: @@ -756,7 +756,7 @@ The *DatabaseService* subclasses provide implementations for the different datab -SaaS customers of CAP applications use the very same techniques than any developer can use to adapt given models or service implementations to their needs. That applies to both, models and service implementations. +SaaS customers of CAP applications use the very same techniques as any developer can use to adapt given models or service implementations to their needs. That applies to both, models and service implementations. ### Extending Models