docs: clarify GitLab CI setup and make GITLAB_API_TOKEN optional clearer

Author: joostboon

docs/cloud/features/ci.mdx

@@ -122,6 +122,8 @@ If you don't specify an `env-id` and the repository is connected to only one env
 
 **Step 1 -- Add the include to your `.gitlab-ci.yml`**
 
+GitLab CI pipelines are configured via a `.gitlab-ci.yml` file in the root of your repository. Add the following `include` block to pull in the Elementary review template. If you already have a `.gitlab-ci.yml`, just add the `include` section to it.
+
 ```yaml
 include:
   - remote: 'https://raw.githubusercontent.com/elementary-data/elementary-ci/v1/templates/mr-review.yml'
@@ -131,10 +133,10 @@ include:
 
 Go to **Settings > CI/CD > Variables** and add:
 
-| Variable | Masked | Description |
-|---|---|---|
-| `ELEMENTARY_API_KEY` | Yes | Your Elementary Cloud API key |
-| `GITLAB_API_TOKEN` | Yes | Optional. Project Access Token with `api` scope. Set this if you cannot enable CI/CD job token API access in project settings. |
+| Variable | Masked | Required | Description |
+|---|---|---|---|
+| `ELEMENTARY_API_KEY` | Yes | Yes | Your Elementary Cloud API key |
+| `GITLAB_API_TOKEN` | Yes | No | Project Access Token with `api` scope. Only needed if you cannot enable CI/CD job token access (see below). |
 
 To post the MR comment, the template uses one of two authentication methods: