chore: copilot review comments

Author: tombojer

products/paas/shopware-paas/account.md

@@ -31,6 +31,8 @@ The available roles depend on the scope:
 * **Project:** `read-only`, `developer`, `admin`
 * **Application:** `read-only`, `developer`, `admin`
 
+In the sections below, the organization role `account-admin` is referred to as Account Admin.
+
 ### Access inheritance
 
 Access is rooted at the organization level.
@@ -40,7 +42,7 @@ To do anything in Shopware PaaS, a user must first be a member of the organizati
 The inheritance model works from broader scope to narrower scope:
 
 * an organization membership is the baseline for any further access
-* an organization admin can also manage project- and application-level access within that organization
+* an Account Admin can also manage project- and application-level access within that organization
 * a project admin also has the effective permissions needed at application level within that project
 
 This means access becomes more specific as you move from organization to project to application, but it always starts with the organization.
@@ -75,8 +77,8 @@ Human users are managed through `account user`. These commands are used to inspe
 
 In practice, there are two common ways to grant human access:
 
-* **Direct grant:** an existing account admin grants a membership directly with `sw-paas account user add`
-* **Access request:** a user requests access themselves with `sw-paas account user request`, and an organization admin later approves or denies that request
+* **Direct grant:** an existing Account Admin grants a membership directly with `sw-paas account user add`
+* **Access request:** a user requests access themselves with `sw-paas account user request`, and an Account Admin later approves or denies that request
 
 The direct grant flow is useful when an admin already knows which user should get which role. The request flow is useful when users need to ask for access to an organization, project, or application on their own.
 
@@ -139,7 +141,7 @@ This is the usual flow:
 
 1. A user creates a request for organization-, project-, or application-level access.
 2. The request stays in `pending` state until it is reviewed.
-3. An organization admin approves or denies the request.
+3. An Account Admin approves or denies the request.
 4. If approved, the membership is created with the requested role.
 5. If denied, no membership is created.
 
@@ -157,13 +159,13 @@ List your own requests:
 sw-paas account user requests list
 ```
 
-Organization admins can list requests for an organization with:
+Account Admins can list requests for an organization with:
 
 ```sh
 sw-paas account user requests list --admin --organization-id <organization-id>
 ```
 
-Organization admins can then approve or deny a pending request:
+Account Admins can then approve or deny a pending request:
 
 ```sh
 sw-paas account user requests resolve

products/paas/shopware-paas/cli-setup.md

@@ -14,10 +14,10 @@ The PaaS CLI is your tool to connect with your PaaS environment, push changes, t
 To install PaaS CLI, run the following command:
 
 ```sh
-curl -sfS https://cli.shopware.com/installer | php
+curl -L https://install.sw-paas-cli.shopware.systems | sh
 ```
 
-When you run the PaaS CLI for the first time, it will ask you to log in via your browser.
+This installs the `sw-paas` binary and adds it to your `PATH` if needed.
 
 You can also generate an SSH key manually and add it in the **My profile > SSH Keys** section of your [PaaS Console](https://console.shopware.com/).
 
@@ -42,7 +42,9 @@ After authentication, you can inspect your current access and manage users or se
 See [Account](account) for:
 
 * `sw-paas account whoami`
-* `sw-paas account context`
+* `sw-paas account context show`
+* `sw-paas account context set`
+* `sw-paas account context delete`
 * user memberships on organization, project, and application level
 * membership requests and approvals
 * service accounts, grants, and tokens

products/paas/shopware-paas/index.md

@@ -65,13 +65,9 @@ git add .
 git commit -am "initial commit"
 ```
 
-7.) Configure the PaaS CLI with your project_id
+7.) Configure the Git remote for your project_id
 
-```sh
-shopware project:set-remote PROJECT_ID
-```
-
-Where PROJECT_ID is the project_id of your empty project.
+Follow the [repository setup guide](repository) to connect your local Git repository to your empty Shopware PaaS project.
 
 8.) Push the code to Shopware PaaS
 
@@ -84,7 +80,7 @@ git push shopware
 The sub-pages describe a more detailed step-by-step guide that you can follow to set up your PaaS project.
 
 First, make sure your [PaaS CLI is set up correctly](cli-setup).
-Once you can authenticate with the CLI, review [account](account) to inspect your own access, manage user memberships, and configure service accounts for automation.
+Once you can authenticate with the CLI, review [Account](account) to inspect your own access, manage user memberships, and configure service accounts for automation.
 Once your PaaS CLI is up and running, it is time to [set up your project repository](repository).
 
 When your repository is set up correctly, you are ready to [push and deploy your project](build-deploy) to the PaaS environment.