Mac -> macOS, no 'WSL'

Author: chgeo

get-started/index.md

@@ -18,7 +18,7 @@ On macOS, Linux and WSL (Windows Subsystem for Linux), we recommend using [Homeb
 ```shell [macOS]
 bash -c "$( curl https://raw.githubusercontent.com/homebrew/install/HEAD/install.sh )"
 ```
-```shell [Linux / WSL]
+```shell [Linux]
 # install curl (required to get Homebrew) and git (required to run Homebrew)
 sudo apt install curl git -y
 bash -c "$( curl https://raw.githubusercontent.com/homebrew/install/HEAD/install.sh )"
@@ -34,7 +34,7 @@ bash -c "$( curl https://raw.githubusercontent.com/homebrew/install/HEAD/install
 ### Node.js and _cds-dk_ {.required}
 
 ::: code-group
-```shell [macOS / Linux / WSL]
+```shell [macOS/Linux]
 brew install node     # Node.js LTS
 npm i -g @sap/cds-dk  # install CAP's cds-dk globally
 ```
@@ -59,7 +59,7 @@ sqlite3 -version
 ### Java and Maven {.optional}
 
 ::: code-group
-```shell [macOS / Linux / WSL]
+```shell [macOS/Linux]
 brew install sapmachine-jdk
 brew install maven
 ```
@@ -92,7 +92,7 @@ brew install git       # Git CLI
 brew install gh        # GitHub CLI
 brew install github    # GitHub Desktop App
 ```
-```shell [Linux / WSL]
+```shell [Linux]
 brew install git       # Git CLI
 brew install gh        # GitHub CLI
 
@@ -127,7 +127,7 @@ git -v # display Git cli version
 ```shell [macOS]
 brew install --cask visual-studio-code            # VS Code itself
 ```
-```bash [Linux / WSL]
+```bash [Linux]
 # VS Code on Homebrew is only supported for macOS
 sudo snap install --classic code
 code -v # display VS Code's version

guides/extensibility/customization.md

@@ -1039,7 +1039,7 @@ In case something unexpected happens, set the variable `DEBUG=cli` in your shell
 
 ::: code-group
 
-```sh [Mac/Linux]
+```sh [macOS/Linux]
 export DEBUG="cli"
 ```
 

guides/services/consuming-services.md

@@ -103,7 +103,7 @@ The export-import cycle is the way to go for now. It is under investigation to i
 
 ::: code-group
 
-```sh [Mac/Linux]
+```sh [macOS/Linux]
 cds compile srv -s OrdersService -2 edmx > OrdersService.edmx
 ```
 
@@ -750,7 +750,7 @@ service RiskService {
 }
 ```
 
-#### Extend a Remote by a Local Service 
+#### Extend a Remote by a Local Service
 
 You can augment a projection with a new association, if the required fields for the on condition are present in the remote service. The use of managed associations isn't possible, because this requires to create new fields in the remote service.
 <!--Does it matter if it's managed or unmanaged? In other section we say, that you shouldn't make it a managed assoc b/c that would lead to runtime errors. -->
@@ -864,7 +864,7 @@ Otherwise, you need to select the source item using that `where` block and take
 [See an example how to handle navigations in Java.](https://github.com/SAP-samples/cloud-cap-risk-management/blob/ext-service-s4hc-suppliers-ui-java/srv/src/main/java/com/sap/cap/riskmanagement/handler/RiskServiceHandler.java){.learn-more .java}
 
 ### Limitations and Feature Matrix
-#### Required Implementations for Mashups 
+#### Required Implementations for Mashups
 
 You need additional logic, if remote entities are in the game. The following table shows what is required. "Local" is a database entity or a projection on a database entity.
 
@@ -1027,7 +1027,7 @@ cds:
 :::
 [Learn more about configuring destinations for Java.](../../java/cqn-services/remote-services){.learn-more}
 
-#### Use Application Defined Destinations 
+#### Use Application Defined Destinations
 
 If you don't want to use SAP BTP destinations, you can also define destinations, which means the URL, authentication type, and additional configuration properties, in your application configuration or code.
 
@@ -1064,9 +1064,9 @@ This is an example of a destination using basic authentication:
 }
 ```
 
-[Learn more about providing project configuration values.](./../../node.js/cds-env#project-specific-configurations){.learn-more} 
+[Learn more about providing project configuration values.](./../../node.js/cds-env#project-specific-configurations){.learn-more}
 
-[See all the supported destination properties.](#destination-properties){.learn-more}  
+[See all the supported destination properties.](#destination-properties){.learn-more}
 
 ::: warning Warning: You should not put any sensitive information here!
 
@@ -1133,7 +1133,7 @@ For the _configuration path_, you **must** use the underscore ("`_`") character
 
 There is no API to create a destination in Node.js programmatically. However, you can change the properties of a remote service before connecting to it, as shown in the previous example.
 
-##### Configure Application Defined Destinations in Java 
+##### Configure Application Defined Destinations in Java
 
 Destinations are configured in Spring Boot's _application.yaml_ file.
 
@@ -1239,7 +1239,7 @@ cds watch --profile hybrid
 If you are developing in the Business Application Studio and want to connect to an on-premise system, you will need to do so via Business Application Studio's built-in proxy, for which you need to add configuration in an `.env` file. See [Connecting to External Systems From the Business Application Studio](https://sap.github.io/cloud-sdk/docs/js/guides/bas) for more details.
 :::
 
-#### Run a Java Application with a Destination 
+#### Run a Java Application with a Destination
 
 Add a new profile `hybrid` to your _application.yaml_ file that configures the destination for the remote service.
 ::: code-group
@@ -1406,13 +1406,13 @@ cds add xsuaa,destination,connectivity
         service: xsuaa
         service-plan: application
         path: ./xs-security.json
-    
+
     - name: cpapp-destination
       type: org.cloudfoundry.managed-service
       parameters:
         service: destination
         service-plan: lite
-    
+
     # Required for on-premise connectivity only
     - name: cpapp-connectivity
       type: org.cloudfoundry.managed-service
@@ -1652,7 +1652,7 @@ The Node.js runtime supports `odata` as an alias for `odata-v4` as well.
 
 The following properties and authentication types are supported for *[application defined destinations](#use-application-defined-destinations)*:
 
-#### Destination Properties 
+#### Destination Properties
 
 These destination properties are fully supported by both, the Java and the Node.js runtime.
 ::: tip

java/developing-applications/building.md

@@ -309,7 +309,7 @@ An example of a CAP application with OData V4 on Cloud Foundry environment:
 Use the following command line to create a project from scratch with the CDS Maven archetype:
 
 ::: code-group
-```sh [Mac/Linux]
+```sh [macOS/Linux]
 mvn archetype:generate -DarchetypeArtifactId=cds-services-archetype -DarchetypeGroupId=com.sap.cds -DarchetypeVersion=RELEASE
 ```
 

node.js/authentication.md

@@ -361,7 +361,7 @@ Please see [`@sap/xssec` documentation](https://www.npmjs.com/package/@sap/xssec
 
 #### XSUAA Fallback
 
-To ease your migration from XSUAA-based to IAS-based authentication, the `ias` strategy automatically supports tokens issued by XSUAA when you provide the necessary credentials at `cds.env.requires.xsuaa.credentials`. 
+To ease your migration from XSUAA-based to IAS-based authentication, the `ias` strategy automatically supports tokens issued by XSUAA when you provide the necessary credentials at `cds.env.requires.xsuaa.credentials`.
 
 For standard bindings, add `xsuaa` to the list of required services as follows:
 
@@ -477,11 +477,11 @@ The following steps assume you've set up the [**Cloud Foundry Command Line Inter
     If you don't know the API endpoint, refer to [Regions and API Endpoints Available for the Cloud Foundry Environment](https://help.sap.com/products/BTP/65de2977205c403bbc107264b8eccf4b/350356d1dc314d3199dca15bd2ab9b0e.html#loiof344a57233d34199b2123b9620d0bb41).
 
 2. Go to the project you have created in [Getting started in a Nutshell](../get-started/bookshop).
- 
+
 #### Configure the Application
 
 1. Configure your app for XSUAA-based authentication if not done yet:
-   
+
     ```sh
     cds add xsuaa --for hybrid
     ```
@@ -602,7 +602,7 @@ The resulting JWT token is sent to the application where it's used to enforce au
 3. In your project folder run:
 
     ::: code-group
-    ```sh [Mac/Linux]
+    ```sh [macOS/Linux]
     cds bind --exec -- npm start --prefix app/router
     ```
     ```cmd [Windows]
@@ -691,7 +691,7 @@ The login fails pointing to the correct OAuth configuration URL that is expected
     cds add ams
     npm install
     ```
-  
+
     This command installs `ams` and `ias` plugins, adds the required dependencies to `package.json` and updates `mta.yaml`.
 
     Learn more about [**Adding AMS Support**](../guides/security/cap-users#adding-ams-support) and [**Adding IAS**](../guides/security/authentication#adding-ias).{.learn-more}
@@ -741,13 +741,13 @@ The login fails pointing to the correct OAuth configuration URL that is expected
     ```
 
 #### Deploy the Application
-  
+
 1. Log in to Cloud Foundry:
     ```sh
     cf l -a <api-endpoint>
     ```
     If you don't know the API endpoint, refer to [Regions and API Endpoints Available for the Cloud Foundry Environment](https://help.sap.com/products/BTP/65de2977205c403bbc107264b8eccf4b/350356d1dc314d3199dca15bd2ab9b0e.html#loiof344a57233d34199b2123b9620d0bb41).
- 
+
 2. Pack and deploy the application:
 
     ```sh
@@ -757,13 +757,13 @@ The login fails pointing to the correct OAuth configuration URL that is expected
 #### Assign Policies in the Administrative Console
 
 1. Log in to your Administrative Console for IAS and go to `Applications & Resources`.
-   
+
    [Learn more about the Administrative Console for IAS.](/@external/guides/security/authentication#ias-admin){.learn-more}
 
 2. Assign policies to IAS users or create custom policies, see [Cloud Deployment](../guides/security/cap-users#ams-deployment).
 
 #### Start Hybrid Testing
- 
+
 1. Bind your local application to the Identity Service Instance:
 
     ```sh
@@ -798,7 +798,7 @@ The login fails pointing to the correct OAuth configuration URL that is expected
 2. In your project folder run:
 
     ::: code-group
-    ```sh [Mac/Linux]
+    ```sh [macOS/Linux]
     cds bind --exec -- npm start --prefix app/router
     ```
     ```cmd [Windows]

node.js/cds-env.md

@@ -406,7 +406,7 @@ cds run --profile my-custom-profile
 or
 
 ::: code-group
-```sh [Mac/Linux]
+```sh [macOS/Linux]
 CDS_ENV=my-custom-profile cds run
 ```
 ```cmd [Windows]

tools/cds-bind.md

@@ -289,7 +289,7 @@ With `cds bind` you avoid storing credentials on your hard disk. If you need to
 For example, you can run the App Router from an `approuter` child directory:
 
 ::: code-group
-```sh [Mac/Linux]
+```sh [macOS/Linux]
 cds bind --exec -- npm start --prefix approuter
 ```
 ```cmd [Windows]
@@ -303,7 +303,7 @@ cds bind --exec '--' npm start --prefix approuter
 This works by constructing a `VCAP_SERVICES` environment variable. You can output the content of this variable as follows:
 
 ::: code-group
-```sh [Mac/Linux]
+```sh [macOS/Linux]
 cds bind --exec -- node -e 'console.log(process.env.VCAP_SERVICES)'
 ```
 ```cmd [Windows]