docs: move "successful auth response" paragraph into the previous bullet

docs/apis-tools/administration-api/authentication.md

@@ -33,7 +33,7 @@ All Administration API requests require authentication. To authenticate, generat
        --data-urlencode "client_id=${CAMUNDA_CONSOLE_CLIENT_ID}" \
        --data-urlencode "client_secret=${CAMUNDA_CONSOLE_CLIENT_SECRET}"
    ```
-5. A successful authentication response looks like the following:
+   A successful authentication response looks like the following:
    ```json
    {
      "access_token": "<TOKEN>",
@@ -43,7 +43,7 @@ All Administration API requests require authentication. To authenticate, generat
      "not-before-policy": 0
    }
    ```
-6. Capture the value of the `access_token` property and store it as your token.
+5. Capture the value of the `access_token` property and store it as your token.
 
 ## Use a token
 

docs/apis-tools/administration-sm-api/administration-sm-api-authentication.md

@@ -20,7 +20,7 @@ All Administration Self-Managed API requests require authentication. To authenti
    --data-urlencode "client_secret=${CLIENT_SECRET}" \
    --data-urlencode 'grant_type=client_credentials'
    ```
-5. A successful authentication response looks like the following:
+   A successful authentication response looks like the following:
    ```json
    {
      "access_token": "<TOKEN>",
@@ -30,7 +30,7 @@ All Administration Self-Managed API requests require authentication. To authenti
      "not-before-policy": 0
    }
    ```
-6. Capture the value of the `access_token` property and store it as your token.
+5. Capture the value of the `access_token` property and store it as your token.
 
 ## Use a token
 

docs/apis-tools/camunda-api-rest/camunda-api-rest-authentication.md

@@ -43,7 +43,7 @@ All Camunda 8 REST API requests require authentication. To authenticate, generat
        --data-urlencode "client_id=${ZEEBE_CLIENT_ID}" \
        --data-urlencode "client_secret=${ZEEBE_CLIENT_SECRET}"
    ```
-5. A successful authentication response looks like the following:
+   A successful authentication response looks like the following:
    ```json
    {
      "access_token": "<TOKEN>",
@@ -53,7 +53,7 @@ All Camunda 8 REST API requests require authentication. To authenticate, generat
      "not-before-policy": 0
    }
    ```
-6. Capture the value of the `access_token` property and store it as your token.
+5. Capture the value of the `access_token` property and store it as your token.
 
 </TabItem>
 
@@ -70,7 +70,7 @@ All Camunda 8 REST API requests require authentication. To authenticate, generat
    --data-urlencode "client_secret=${CLIENT_SECRET}" \
    --data-urlencode 'grant_type=client_credentials'
    ```
-5. A successful authentication response looks like the following:
+   A successful authentication response looks like the following:
    ```json
    {
      "access_token": "<TOKEN>",
@@ -80,7 +80,7 @@ All Camunda 8 REST API requests require authentication. To authenticate, generat
      "not-before-policy": 0
    }
    ```
-6. Capture the value of the `access_token` property and store it as your token.
+5. Capture the value of the `access_token` property and store it as your token.
 
 </TabItem>
 

docs/apis-tools/operate-api/authentication.md

@@ -42,7 +42,7 @@ All Operate REST API requests require authentication. To authenticate, generate
        --data-urlencode "client_id=${ZEEBE_CLIENT_ID}" \
        --data-urlencode "client_secret=${ZEEBE_CLIENT_SECRET}"
    ```
-5. A successful authentication response looks like the following:
+   A successful authentication response looks like the following:
    ```json
    {
      "access_token": "<TOKEN>",
@@ -52,7 +52,7 @@ All Operate REST API requests require authentication. To authenticate, generate
      "not-before-policy": 0
    }
    ```
-6. Capture the value of the `access_token` property and store it as your token.
+5. Capture the value of the `access_token` property and store it as your token.
 
 </TabItem>
 
@@ -69,7 +69,7 @@ All Operate REST API requests require authentication. To authenticate, generate
    --data-urlencode "client_secret=${CLIENT_SECRET}" \
    --data-urlencode 'grant_type=client_credentials'
    ```
-5. A successful authentication response looks like the following:
+   A successful authentication response looks like the following:
    ```json
    {
      "access_token": "<TOKEN>",
@@ -79,7 +79,7 @@ All Operate REST API requests require authentication. To authenticate, generate
      "not-before-policy": 0
    }
    ```
-6. Capture the value of the `access_token` property and store it as your token.
+5. Capture the value of the `access_token` property and store it as your token.
 
 See the [Operate Configuration - Authentication](/self-managed/operate-deployment/operate-authentication.md#identity) documentation for more information about this authentication method.
 

docs/apis-tools/tasklist-api-rest/tasklist-api-rest-authentication.md

@@ -42,7 +42,7 @@ All Tasklist API requests require authentication. To authenticate, generate a [J
        --data-urlencode "client_id=${ZEEBE_CLIENT_ID}" \
        --data-urlencode "client_secret=${ZEEBE_CLIENT_SECRET}"
    ```
-5. A successful authentication response looks like the following:
+   A successful authentication response looks like the following:
    ```json
    {
      "access_token": "<TOKEN>",
@@ -52,7 +52,7 @@ All Tasklist API requests require authentication. To authenticate, generate a [J
      "not-before-policy": 0
    }
    ```
-6. Capture the value of the `access_token` property and store it as your token.
+5. Capture the value of the `access_token` property and store it as your token.
 
 </TabItem>
 
@@ -69,7 +69,7 @@ All Tasklist API requests require authentication. To authenticate, generate a [J
    --data-urlencode "client_secret=${CLIENT_SECRET}" \
    --data-urlencode 'grant_type=client_credentials'
    ```
-5. A successful authentication response looks like the following:
+   A successful authentication response looks like the following:
    ```json
    {
      "access_token": "<TOKEN>",
@@ -79,7 +79,7 @@ All Tasklist API requests require authentication. To authenticate, generate a [J
      "not-before-policy": 0
    }
    ```
-6. Capture the value of the `access_token` property and store it as your token.
+5. Capture the value of the `access_token` property and store it as your token.
 
 See the [Tasklist Configuration - Authentication](/self-managed/tasklist-deployment/tasklist-authentication.md#identity) documentation for more information about this authentication method.
 

docs/apis-tools/web-modeler-api/authentication.md

@@ -44,7 +44,7 @@ All Web Modeler API requests require authentication. To authenticate, generate a
        --data-urlencode "client_id=${CAMUNDA_CONSOLE_CLIENT_ID}" \
        --data-urlencode "client_secret=${CAMUNDA_CONSOLE_CLIENT_SECRET}"
    ```
-5. A successful authentication response looks like the following:
+   A successful authentication response looks like the following:
    ```json
    {
      "access_token": "<TOKEN>",
@@ -54,7 +54,7 @@ All Web Modeler API requests require authentication. To authenticate, generate a
      "not-before-policy": 0
    }
    ```
-6. Capture the value of the `access_token` property and store it as your token.
+5. Capture the value of the `access_token` property and store it as your token.
 
 </TabItem>
 
@@ -71,7 +71,7 @@ All Web Modeler API requests require authentication. To authenticate, generate a
    --data-urlencode "client_secret=${CLIENT_SECRET}" \
    --data-urlencode 'grant_type=client_credentials'
    ```
-5. A successful authentication response looks like the following:
+   A successful authentication response looks like the following:
    ```json
    {
      "access_token": "<TOKEN>",
@@ -81,7 +81,7 @@ All Web Modeler API requests require authentication. To authenticate, generate a
      "not-before-policy": 0
    }
    ```
-6. Capture the value of the `access_token` property and store it as your token.
+5. Capture the value of the `access_token` property and store it as your token.
 
 </TabItem>
 

docs/apis-tools/zeebe-api-rest/zeebe-api-rest-authentication.md

@@ -42,7 +42,7 @@ All Zeebe REST API requests require authentication. To authenticate, generate a
        --data-urlencode "client_id=${ZEEBE_CLIENT_ID}" \
        --data-urlencode "client_secret=${ZEEBE_CLIENT_SECRET}"
    ```
-5. A successful authentication response looks like the following:
+   A successful authentication response looks like the following:
    ```json
    {
      "access_token": "<TOKEN>",
@@ -52,7 +52,7 @@ All Zeebe REST API requests require authentication. To authenticate, generate a
      "not-before-policy": 0
    }
    ```
-6. Capture the value of the `access_token` property and store it as your token.
+5. Capture the value of the `access_token` property and store it as your token.
 
 </TabItem>
 
@@ -69,7 +69,7 @@ All Zeebe REST API requests require authentication. To authenticate, generate a
    --data-urlencode "client_secret=${CLIENT_SECRET}" \
    --data-urlencode 'grant_type=client_credentials'
    ```
-5. A successful authentication response looks like the following:
+   A successful authentication response looks like the following:
    ```json
    {
      "access_token": "<TOKEN>",
@@ -79,7 +79,7 @@ All Zeebe REST API requests require authentication. To authenticate, generate a
      "not-before-policy": 0
    }
    ```
-6. Capture the value of the `access_token` property and store it as your token.
+5. Capture the value of the `access_token` property and store it as your token.
 
 </TabItem>
 

optimize/apis-tools/optimize-api/optimize-api-authentication.md

@@ -41,7 +41,7 @@ All Optimize API requests except [the health readiness endpoint](./health-readin
        --data-urlencode "client_id=${ZEEBE_CLIENT_ID}" \
        --data-urlencode "client_secret=${ZEEBE_CLIENT_SECRET}"
    ```
-5. A successful authentication response looks like the following:
+   A successful authentication response looks like the following:
    ```json
    {
      "access_token": "<TOKEN>",
@@ -51,7 +51,7 @@ All Optimize API requests except [the health readiness endpoint](./health-readin
      "not-before-policy": 0
    }
    ```
-6. Capture the value of the `access_token` property and store it as your token.
+5. Capture the value of the `access_token` property and store it as your token.
 
 </TabItem>
 
@@ -69,7 +69,7 @@ All Optimize API requests except [the health readiness endpoint](./health-readin
    --data-urlencode "client_secret=${CLIENT_SECRET}" \
    --data-urlencode 'grant_type=client_credentials'
    ```
-6. A successful authentication response looks like the following:
+   A successful authentication response looks like the following:
    ```json
    {
      "access_token": "<TOKEN>",
@@ -79,7 +79,7 @@ All Optimize API requests except [the health readiness endpoint](./health-readin
      "not-before-policy": 0
    }
    ```
-7. Capture the value of the `access_token` property and store it as your token.
+6. Capture the value of the `access_token` property and store it as your token.
 
 :::note
 The Optimize API can also be configured in a Self-Managed environment to authenticate with a single shared access token. Refer to [Public API Configuration](/self-managed/optimize-deployment/configuration/system-configuration.md#public-api) for the configuration required to access the public API using a specific token.

optimize_versioned_docs/version-3.13.0/apis-tools/optimize-api/optimize-api-authentication.md

@@ -41,7 +41,7 @@ All Optimize API requests except [the health readiness endpoint](./health-readin
        --data-urlencode "client_id=${ZEEBE_CLIENT_ID}" \
        --data-urlencode "client_secret=${ZEEBE_CLIENT_SECRET}"
    ```
-5. A successful authentication response looks like the following:
+   A successful authentication response looks like the following:
    ```json
    {
      "access_token": "<TOKEN>",
@@ -51,7 +51,7 @@ All Optimize API requests except [the health readiness endpoint](./health-readin
      "not-before-policy": 0
    }
    ```
-6. Capture the value of the `access_token` property and store it as your token.
+5. Capture the value of the `access_token` property and store it as your token.
 
 </TabItem>
 
@@ -69,7 +69,7 @@ All Optimize API requests except [the health readiness endpoint](./health-readin
    --data-urlencode "client_secret=${CLIENT_SECRET}" \
    --data-urlencode 'grant_type=client_credentials'
    ```
-6. A successful authentication response looks like the following:
+   A successful authentication response looks like the following:
    ```json
    {
      "access_token": "<TOKEN>",
@@ -79,7 +79,7 @@ All Optimize API requests except [the health readiness endpoint](./health-readin
      "not-before-policy": 0
    }
    ```
-7. Capture the value of the `access_token` property and store it as your token.
+6. Capture the value of the `access_token` property and store it as your token.
 
 :::note
 The Optimize API can also be configured in a Self-Managed environment to authenticate with a single shared access token. Refer to [Public API Configuration](/self-managed/optimize-deployment/configuration/system-configuration.md#public-api) for the configuration required to access the public API using a specific token.

versioned_docs/version-8.5/apis-tools/administration-api/authentication.md

@@ -33,7 +33,7 @@ All Administration API requests require authentication. To authenticate, generat
        --data-urlencode "client_id=${CAMUNDA_CONSOLE_CLIENT_ID}" \
        --data-urlencode "client_secret=${CAMUNDA_CONSOLE_CLIENT_SECRET}"
    ```
-5. A successful authentication response looks like the following:
+   A successful authentication response looks like the following:
    ```json
    {
      "access_token": "<TOKEN>",
@@ -43,7 +43,7 @@ All Administration API requests require authentication. To authenticate, generat
      "not-before-policy": 0
    }
    ```
-6. Capture the value of the `access_token` property and store it as your token.
+5. Capture the value of the `access_token` property and store it as your token.
 
 ## Use a token
 

versioned_docs/version-8.5/apis-tools/operate-api/authentication.md

@@ -42,7 +42,7 @@ All Operate REST API requests require authentication. To authenticate, generate
        --data-urlencode "client_id=${ZEEBE_CLIENT_ID}" \
        --data-urlencode "client_secret=${ZEEBE_CLIENT_SECRET}"
    ```
-5. A successful authentication response looks like the following:
+   A successful authentication response looks like the following:
    ```json
    {
      "access_token": "<TOKEN>",
@@ -52,7 +52,7 @@ All Operate REST API requests require authentication. To authenticate, generate
      "not-before-policy": 0
    }
    ```
-6. Capture the value of the `access_token` property and store it as your token.
+5. Capture the value of the `access_token` property and store it as your token.
 
 </TabItem>
 
@@ -69,7 +69,7 @@ All Operate REST API requests require authentication. To authenticate, generate
    --data-urlencode "client_secret=${CLIENT_SECRET}" \
    --data-urlencode 'grant_type=client_credentials'
    ```
-5. A successful authentication response looks like the following:
+   A successful authentication response looks like the following:
    ```json
    {
      "access_token": "<TOKEN>",
@@ -79,7 +79,7 @@ All Operate REST API requests require authentication. To authenticate, generate
      "not-before-policy": 0
    }
    ```
-6. Capture the value of the `access_token` property and store it as your token.
+5. Capture the value of the `access_token` property and store it as your token.
 
 See the [Operate Configuration - Authentication](/self-managed/operate-deployment/operate-authentication.md#identity) documentation for more information about this authentication method.
 

versioned_docs/version-8.5/apis-tools/tasklist-api-rest/tasklist-api-rest-authentication.md

@@ -42,7 +42,7 @@ All Tasklist API requests require authentication. To authenticate, generate a [J
        --data-urlencode "client_id=${ZEEBE_CLIENT_ID}" \
        --data-urlencode "client_secret=${ZEEBE_CLIENT_SECRET}"
    ```
-5. A successful authentication response looks like the following:
+   A successful authentication response looks like the following:
    ```json
    {
      "access_token": "<TOKEN>",
@@ -52,7 +52,7 @@ All Tasklist API requests require authentication. To authenticate, generate a [J
      "not-before-policy": 0
    }
    ```
-6. Capture the value of the `access_token` property and store it as your token.
+5. Capture the value of the `access_token` property and store it as your token.
 
 </TabItem>
 
@@ -69,7 +69,7 @@ All Tasklist API requests require authentication. To authenticate, generate a [J
    --data-urlencode "client_secret=${CLIENT_SECRET}" \
    --data-urlencode 'grant_type=client_credentials'
    ```
-5. A successful authentication response looks like the following:
+   A successful authentication response looks like the following:
    ```json
    {
      "access_token": "<TOKEN>",
@@ -79,7 +79,7 @@ All Tasklist API requests require authentication. To authenticate, generate a [J
      "not-before-policy": 0
    }
    ```
-6. Capture the value of the `access_token` property and store it as your token.
+5. Capture the value of the `access_token` property and store it as your token.
 
 See the [Tasklist Configuration - Authentication](/self-managed/tasklist-deployment/tasklist-authentication.md#identity) documentation for more information about this authentication method.