diff --git a/content/actions/security-guides/automatic-token-authentication.md b/content/actions/security-guides/automatic-token-authentication.md
index cba9c87b4c..f48f8f759b 100644
--- a/content/actions/security-guides/automatic-token-authentication.md
+++ b/content/actions/security-guides/automatic-token-authentication.md
@@ -40,7 +40,7 @@ You can use the `GITHUB_TOKEN` by using the standard syntax for referencing secr
 {% endnote %}
 {% endif %}
 
-{% data reusables.github-actions.actions-do-not-trigger-workflows %} 
+{% data reusables.github-actions.actions-do-not-trigger-workflows %}
 
 ### Example 1: passing the `GITHUB_TOKEN` as an input
 
@@ -106,7 +106,7 @@ The following table shows the permissions granted to the `GITHUB_TOKEN` by defau
 | checks        | read/write  | none | read |
 | contents      | read/write  | read | read |
 | deployments   | read/write  | none | read |
-| id_token      | read/write  | none | read |
+| id-token      | read/write  | none | read |
 | issues        | read/write  | none | read |
 | metadata      | read        | read | read |
 | packages      | read/write  | none | read |
@@ -142,7 +142,7 @@ You can use the `permissions` key in your workflow file to modify permissions fo
 
 {% data reusables.github-actions.forked-write-permission %}
 
-The two workflow examples earlier in this article show the `permissions` key being used at the workflow level, and at the job level. In [Example 1](#example-1-passing-the-github_token-as-an-input) the two permissions are specified for the entire workflow. In [Example 2](#example-2-calling-the-rest-api) write access is granted for one scope for a single job. 
+The two workflow examples earlier in this article show the `permissions` key being used at the workflow level, and at the job level. In [Example 1](#example-1-passing-the-github_token-as-an-input) the two permissions are specified for the entire workflow. In [Example 2](#example-2-calling-the-rest-api) write access is granted for one scope for a single job.
 
 For full details of the `permissions` key, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#permissions)."
 
diff --git a/data/reusables/github-actions/github-token-available-permissions.md b/data/reusables/github-actions/github-token-available-permissions.md
index 79dec2bfd8..3ad79da348 100644
--- a/data/reusables/github-actions/github-token-available-permissions.md
+++ b/data/reusables/github-actions/github-token-available-permissions.md
@@ -6,7 +6,7 @@ permissions:
   checks: read|write|none
   contents: read|write|none
   deployments: read|write|none
-  id_token: read|write|none
+  id-token: read|write|none
   issues: read|write|none
   discussions: read|write|none
   packages: read|write|none
@@ -16,7 +16,7 @@ permissions:
   statuses: read|write|none
 ```
 
-If you specify the access for any of these scopes, all of those that are not specified are set to `none`. 
+If you specify the access for any of these scopes, all of those that are not specified are set to `none`.
 
 You can use the following syntax to define read or write access for all of the available scopes: