diff --git a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md
index 3638e5d3cbe2..144ad2f415e2 100644
--- a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md
+++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md
@@ -85,6 +85,10 @@ After changing your username, links to your previous profile page, such as `http
 
 After changing your username, the URLs to any public or secret gists will also change and previous links to these will return a 404 error. We recommend updating the links to these gists anywhere you may have shared them.
 
+## CODEOWNERS files
+
+After changing your username, CODEOWNERS files that include your old username will need to be manually updated. When you view the CODEOWNERS files on {% data variables.product.prodname_dotcom_the_website %}, an error message is displayed if the file contains any unknown users, or users without write access. We recommend updating all relevant CODEOWNERS files with your new username. For more information, see "[About code owners](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners)."
+
 ## Changing your username
 
 {% data reusables.user-settings.access_settings %}
diff --git a/content/actions/using-jobs/using-conditions-to-control-job-execution.md b/content/actions/using-jobs/using-conditions-to-control-job-execution.md
index 0bd46fa968be..091a2e0712e2 100644
--- a/content/actions/using-jobs/using-conditions-to-control-job-execution.md
+++ b/content/actions/using-jobs/using-conditions-to-control-job-execution.md
@@ -26,3 +26,9 @@ miniTocMaxHeadingLevel: 4
 You would see the following status on a skipped job:
 
 ![Skipped-required-run-details](/assets/images/help/repository/skipped-required-run-details.png)
+
+{% note %}
+
+**Note:** In some parts of the workflow you cannot use environment variables. Instead you can use contexts to access the value of an environment variable. For more information, see "[Using the env context to access environment variable values](/actions/learn-github-actions/variables#using-the-env-context-to-access-environment-variable-values)."
+
+{% endnote %}