github · docs-bot · Aug 10, 2026 · Aug 10, 2026 · Aug 10, 2026 · Aug 10, 2026
diff --git a/content/actions/reference/workflows-and-actions/workflow-syntax.md b/content/actions/reference/workflows-and-actions/workflow-syntax.md
@@ -283,7 +283,7 @@ The value of this parameter is a string specifying the data type of the input. T
 
 {% data reusables.actions.forked-write-permission %}
 
-## How permissions are calculated for a workflow job
+### How permissions are calculated for a workflow job
 
 The permissions for the `GITHUB_TOKEN` are initially set to the default setting for the enterprise, organization, or repository. If the default is set to the restricted permissions at any of these levels then this will apply to the relevant repositories. For example, if you choose the restricted default at the organization level then all repositories in that organization will use the restricted permissions as the default. The permissions are then adjusted based on any configuration within the workflow file, first at the workflow level and then at the job level. Finally, if the workflow was triggered by a pull request event other than `pull_request_target` from a forked repository, and the **Send write tokens to workflows from pull requests** setting is not selected, the permissions are adjusted to change any write permissions to read only.
 

diff --git a/...nt/pull-requests/how-tos/create-pull-requests/creating-stacked-pull-requests.md b/...nt/pull-requests/how-tos/create-pull-requests/creating-stacked-pull-requests.md
@@ -21,7 +21,7 @@ Create stacked pull requests with the `gh stack` extension in {% data variables.
 1. Initialize a stack. This creates and checks out the first branch on top of your trunk branch.
 
    ```shell copy
-   gh stack init auth-layer
+   gh stack init BRANCH-NAME
    ```
 
 1. Write code for the first layer, then stage and commit your changes.

diff --git a/package-lock.json b/package-lock.json