Fixed more links to capire/samples

Author: danjoa

get-started/learning-sources.md

@@ -100,7 +100,7 @@ In here, we collected several interesting sample projects for you. Not all of th
 ### Bookshop by capire {.github}
 
 > [![]()](https://github.com/sap-samples/cloud-cap-samples-java){.java}
-> [![]()](https://github.com/sap-samples/cloud-cap-samples){.node}
+> [![]()](https://github.com/capire/bookshop){.node}
 
 The bookshop sample is our original sample provided by the CAP team and featured in the [getting started guides](../get-started/in-a-nutshell).
 It's available in both Node.js and Java. The Node.js variant contains additional samples besides bookshop that demonstrate various features of CAP.

guides/data-privacy/pdm.md

@@ -101,7 +101,7 @@ Make sure to have [indicated all relevant entities and elements in your domain m
 
 As an additional step, you have to create flat projections on the additional business data, like transactional data.
 
-In our model, we have `Incidents` and `Conversations`, which are connected via a [composition](https://github.com/SAP-samples/cloud-cap-samples/blob/gdpr/orders/db/schema.cds). Since SAP Personal Data Manager needs flattened out structures, we define a helper view `IncidentConversationView` to flatten this out.
+In our model, we have `Incidents` and `Conversations`, which are connected via a composition. Since SAP Personal Data Manager needs flattened out structures, we define a helper view `IncidentConversationView` to flatten this out.
 
 We have to then add data privacy-specific annotations to this new view as well. The `IncidentConversationView` as transactional data is marked as `Other`. In addition, it is important to tag the correct field, which defines the corresponding data subject, in our case that is `customer_ID @PersonalData.FieldSemantics: 'DataSubjectID';`
 

guides/databases-sqlite.md

@@ -317,7 +317,7 @@ The following is an overview of advanced features supported by the new database
 
 ### Path Expressions & Filters {.node}
 
-The new database service provides **full support** for all kinds of [path expressions](../cds/cql#path-expressions), including [infix filters](../cds/cql#with-infix-filters) and [exists predicates](../cds/cql#exists-predicate). For example, you can try this out with *[cap/samples](https://github.com/sap-samples/cloud-cap-samples)* as follows:
+The new database service provides **full support** for all kinds of [path expressions](../cds/cql#path-expressions), including [infix filters](../cds/cql#with-infix-filters) and [exists predicates](../cds/cql#exists-predicate). For example, you can try this out with *[@capire/samples](https://github.com/capire/samples)* as follows:
 
 ```js
 // $ cds repl --profile better-sqlite

guides/deployment/microservices.md

@@ -39,7 +39,7 @@ This guide describes a way to manage development and deployment via *[monorepos]
 
    ```sh
    git init
-   git submodule add https://github.com/capire/bookstore 
+   git submodule add https://github.com/capire/bookstore
    git submodule add https://github.com/capire/reviews
    git submodule add https://github.com/capire/orders
    git submodule add https://github.com/capire/common
@@ -53,7 +53,7 @@ This guide describes a way to manage development and deployment via *[monorepos]
    node_modules
    gen
    ```
-   > The outcome of this looks and behaves exactly as the monorepo layout in *[cap/samples](https://github.com/sap-samples/cloud-cap-samples)*,  so we can exercise the subsequent steps in there...
+   > The outcome of this looks and behaves exactly as the monorepo layout in *[cap/samples](https://github.com/capire/samples)*,  so we can exercise the subsequent steps in there...
 
 3. Test-drive locally:
    ```sh
@@ -71,7 +71,7 @@ This guide describes a way to manage development and deployment via *[monorepos]
    Each microservice can be started independently. If you start each microservice, one after the other in a different terminal, the connection is already established.
 
    [Learn more about Automatic Bindings by `cds watch`](../extensibility/composition#bindings-via-cds-watch){.learn-more}
-   
+
 
 ::: details The project structure
 
@@ -148,7 +148,7 @@ These are the (not so beneficial) side effects you when using a shared persisten
    ```
    :::
 
-   > Note: the `using` directives refer to `index.cds` files existing in the target packages. Your projects may have different entry points. 
+   > Note: the `using` directives refer to `index.cds` files existing in the target packages. Your projects may have different entry points.
 
 ::: details Try it out
 
@@ -176,7 +176,7 @@ cds build --for hana
 cd ..
 ```
 
-> Note: As we can see in the output for `cds deploy` and `cds build`, it also correctly collects and adds all initial data from enclosed `.csv` files. 
+> Note: As we can see in the output for `cds deploy` and `cds build`, it also correctly collects and adds all initial data from enclosed `.csv` files.
 :::
 
 ::: details Other project structures
@@ -208,7 +208,7 @@ This section is about how to deploy all 3+1 projects at once with a common _mta.
 
 ![component diagram with synchronous and event communication for orders](./assets/microservices/bookstore.excalidraw.svg)
 
-[cap-samples](https://github.com/SAP-samples/cloud-cap-samples?tab=readme-ov-file#welcome-to-capsamples) already has an all-in-one deployment implemented. Similar steps are necessary to convert projects with multiple CAP applications into a shared database deployment.
+[@capire/samples](https://github.com/capire/samples#readme) already has an all-in-one deployment implemented. Similar steps are necessary to convert projects with multiple CAP applications into a shared database deployment.
 
 ### Deployment Descriptor
 
@@ -403,7 +403,7 @@ Add the admin role
 ::: details Configure each app for cloud readiness
 Add NPM dependency `@sap/xssec`:
 
-```shell  
+```shell
 npm i @sap/xssec --workspace bookstore
 npm i @sap/xssec --workspace orders
 npm i @sap/xssec --workspace reviews
@@ -1024,7 +1024,7 @@ In the bookstore example, while reviews may be down, orders may still be possibl
 
 This benefit is null for apps with synchronous dependencies on each other. If A depends on synchronous calls to B, then if B is down, A is down as well.
 
-### Multiple Deployment Units 
+### Multiple Deployment Units
 
 With multiple apps, you can still deploy them together as one unit, for example as part of a multitarget application archive.
 Once an application grows bigger, this takes a significant amount of time.

guides/deployment/to-cf.md

@@ -42,7 +42,7 @@ cd bookshop
 
 ::: details Alternatively, download or clone the sample repository
 
-Exercise the following steps in the `bookshop` sample of the [`capire`](https://github.com/sap-samples/cloud-cap-samples) org:
+Exercise the following steps in the [`@capire/bookshop` sample](https://github.com/capire/bookshop):
 
 ```sh
 git clone https://github.com/capire/bookshop

node.js/cds-connect.md

@@ -126,7 +126,7 @@ Prefix the module path in `impl` with `./` to refer to a file relative to your p
 
 ### cds.requires.<i>\<srv\></i>`.kind`
 
-As service configurations inherit from each other along `kind` chains, we can refer to default configurations shipped with `@sap/cds`, as you commonly see that in our [_cap/samples_](https://github.com/sap-samples/cloud-cap-samples), like so:
+As service configurations inherit from each other along `kind` chains, we can refer to default configurations shipped with `@sap/cds`, as you commonly see that in our [_cap/samples_](https://github.com/capire/samples), like so:
 
 ```json
 "cds": { "requires": {
@@ -409,11 +409,11 @@ If the `vcap` configuration contains multiple properties such as `name`, `label`
   "cds": {
     "requires": {
       "hana": {
-        "vcap": { 
-          "label": "hana", 
-          "plan": "standard", 
-          "name": "myHana", 
-          "tags": "database" 
+        "vcap": {
+          "label": "hana",
+          "plan": "standard",
+          "name": "myHana",
+          "tags": "database"
         }
       }
     }
@@ -465,10 +465,10 @@ CAP services often come with a default `vcap` configuration. In rare cases, the
   "cds": {
     "requires": {
       "hana": {
-        "vcap": { 
-          "label": false,  
-          "name": "myHana", 
-          "tags": "database" 
+        "vcap": {
+          "label": false,
+          "name": "myHana",
+          "tags": "database"
         }
       }
     }

node.js/cds-i18n.md

@@ -261,7 +261,7 @@ msg.for('OUT_OF_RANGE', {val:0,min:1,max:11}) //> 0 is not in range 1..11
 
 #### Looking up labels for CSN definitions
 
-You can alternatively pass in a CSN definition instead of an i18n key to look up the localized UI label for that an entity or element. For example, try this in `cds repl` from within the [*cap/samples* root folder](https://github.com/sap-samples/cloud-cap-samples): {.indent}
+You can alternatively pass in a CSN definition instead of an i18n key to look up the localized UI label for that an entity or element. For example, try this in `cds repl` from within the [*cap/samples* root folder](https://github.com/capire/samples): {.indent}
 
 ```js
 [dev] cds repl
@@ -344,8 +344,7 @@ Instances of this class are used through [`I18nBundle.files`](#files) to fetch a
 
 By default fetches i18n folders and files from the [neighborhood](#from-models-neighborhood) of a given model's sources, by default using `cds.model`.
 
-
-For example, try this in `cds repl` run from the project root of *[cap/samples](https://github.com/sap-samples/cloud-cap-samples)*:
+For example, try this in `cds repl` run from the project root of *[cap/samples](https://github.com/capire/samples)*:
 
 ```js
 [dev] cds repl
@@ -459,7 +458,7 @@ In effect i18n folders and hence files are fetched from the neighborhood of the
 
 #### 1. Starting from the current model's `$sources`
 
-For example given these model sources from [cap/samples](https://github.com/sap-samples/cloud-cap-samples):
+For example given these model sources from [cap/samples](https://github.com/capire/samples):
 
 ```js
 [dev] cds repl

node.js/cds-test.md

@@ -585,7 +585,7 @@ describe(() => { cds.test(...) })
 
 ## Using `cds.test` in REPL
 
-You can use `cds.test` in REPL, for example, by running this from your command line in [*cap/samples*](https://github.com/sap-samples/cloud-cap-samples):
+You can use `cds.test` in REPL, for example, by running this from your command line in [*cap/samples*](https://github.com/capire/samples):
 
 ```sh
 [cap/samples] cds repl