[Improvement]: Fix duplicate headers for Core Productivity (github#34405

)

Co-authored-by: Peter Bengtsson <[email protected]>
Co-authored-by: Laura Coursen <[email protected]>

content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md

@@ -17,10 +17,12 @@ topics:
   - Notifications
 shortTitle: Find your username or email
 ---
-{% mac %}
+
 
 ## {% data variables.product.prodname_desktop %} users
 
+{% mac %}
+
 1. In the **GitHub Desktop** menu, click **Preferences**.
 2. In the Preferences window, verify the following:
     - To view your {% data variables.product.product_name %} username, click **Accounts**.
@@ -30,13 +32,11 @@ shortTitle: Find your username or email
 
 {% windows %}
 
-## {% data variables.product.prodname_desktop %} users
-
 1. In the **File** menu, click **Options**.
 2. In the Options window, verify the following:
     - To view your {% data variables.product.product_name %} username, click **Accounts**.
     - To view your Git email, click **Git**. Note that this email is not guaranteed to be [your primary {% data variables.product.product_name %} email](/articles/changing-your-primary-email-address).
-  
+
 {% endwindows %}
 
 ## Finding your username in your `user.name` configuration

content/billing/managing-your-github-billing-settings/setting-your-billing-email.md

@@ -45,15 +45,15 @@ If you have users that want to receive billing reports, you can add their email
 
 {% data reusables.dotcom_billing.org-billing-perms %}
 
-### Adding a recipient for billing notifications
+### Adding a recipient for billing notifications for your organization
 
 {% data reusables.organizations.billing-settings %}
 1. Under "Billing management", to the right of "Email recipients", click **Add**.
   ![Add recipient](/assets/images/help/billing/billing-add-email-recipient.png)
 1. Type the email address of the recipient, then click **Add**.
   ![Add recipient modal](/assets/images/help/billing/billing-add-email-recipient-modal.png)
 
-### Changing the primary recipient for billing notifications
+### Changing the primary recipient for billing notifications for your organization
 
 One address must always be designated as the primary recipient. The address with this designation can't be removed until a new primary recipient is selected.
 
@@ -62,7 +62,7 @@ One address must always be designated as the primary recipient. The address with
 1. To the right of the email address, use the "Edit" drop-down menu, and click **Mark as primary**.
   ![Mark primary recipient](/assets/images/help/billing/billing-change-primary-email-recipient.png)
 
-### Removing a recipient from billing notifications
+### Removing a recipient from billing notifications for your organization
 
 {% data reusables.organizations.billing-settings %}
 1. Under "Email recipients", find the email address you want to remove.
@@ -82,35 +82,35 @@ Only enterprise members with the owner or billing manager role can access or cha
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.billing-tab %}
-1. Click **Billing emails**. 
+1. Click **Billing emails**.
 2. Under "Email recipients", to the right of the billing email address, click **Edit**.
   ![Screenshot of the current billing email with the edit button emphasized](/assets/images/help/billing/billing-change-email.png)
 2. Type a valid email address, then click **Update**.
   ![Screenshot of the edit billing email address modal window with a sample email address entered](/assets/images/help/billing/billing-change-email-modal.png)
 
 ## Managing additional recipients for your enterprise's billing email
 
-If you have users that want to receive billing reports, you can add their email addresses as billing email recipients. 
+If you have users that want to receive billing reports, you can add their email addresses as billing email recipients.
 
 Only enterprise members with the owner or billing manager role can access or change billing settings for your enterprise. For more information, see "[Managing users in your enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)."
 
-### Adding a recipient for billing notifications
+### Adding a recipient for billing notifications for your enterprise
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.billing-tab %}
-1. Click **Billing emails**. 
+1. Click **Billing emails**.
 2. Under "Email recipients", to the right of the billing email address, click **Add**.
    ![Screenshot of the current billing email with the add button emphasized](/assets/images/help/billing/billing-add-email-recipient.png)
 3. Type the email address of the recipient, then click **Add**.
    ![Screenshot of the add billing email address modal window without a sample email address entered](/assets/images/help/billing/billing-add-email-recipient-modal.png)
 
-### Removing a recipient from billing notifications
+### Removing a recipient from billing notifications for your enterprise
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.billing-tab %}
-1. Click **Billing emails**. 
+1. Click **Billing emails**.
 2. Under "Email recipients", find the email address you want to remove.
 3. For the user's entry in the list, click **Edit**.
    ![Screenshot of the recipient's email with the edit button emphasized](/assets/images/help/billing/billing-edit-email-recipient.png)

content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms.md

@@ -15,7 +15,7 @@ topics:
 
 The template does not contain a `name` field, which means it is not clear what to call your issue template when giving users a list of options.
 
-### Example
+### Example of "required top level key `name` is missing" error
 
 ```yaml
 description: "Thank you for reporting a bug!"
@@ -34,7 +34,7 @@ description: "Thank you for reporting a bug!"
 
 This error message means that a permitted key has been provided, but its value cannot be parsed as the data type is not supported.
 
-### Example
+### Example of "`key` must be a string" error
 
 The `description` below is being parsed as a Boolean, but it should be a string.
 
@@ -73,7 +73,7 @@ description: "File a bug report"
 
 An unexpected key was supplied at the top level of the template. For more information about which top-level keys are supported, see "[Syntax for issue forms](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms#top-level-syntax)."
 
-### Example
+### Example of "`input` is not a permitted key" error
 
 ```yaml
 name: "Bug report"
@@ -100,7 +100,7 @@ The error can be fixed by removing the forbidden keys.
 
 Issue forms must accept user input, which means that at least one of its fields must contain a user input field. A `markdown` element is static text, so a `body` array cannot contain only `markdown` elements.
 
-### Example
+### Example of "body must contain at least one non-markdown field" error
 
 ```yaml
 name: "Bug report"
@@ -127,7 +127,7 @@ body:
 
 If using `id` attributes to distinguish multiple elements, each `id` attribute must be unique.
 
-### Example
+### Example of "body must have unique ids" error
 
 ```yaml
 name: "Bug report"
@@ -161,7 +161,7 @@ body:
 
 When there are multiple `body` elements that accept user input, the `label` attribute for each user input field must be unique.
 
-### Example
+### Example of "body must have unique labels" error
 
 ```yaml
 name: "Bug report"
@@ -209,7 +209,7 @@ body:
 
 Similar labels may be processed into identical references. If an `id` attribute is not provided for an `input`, the `label` attribute is used to generate a reference to the `input` field. To do this, we process the `label` by leveraging the Rails [parameterize](https://apidock.com/rails/ActiveSupport/Inflector/parameterize) method. In some cases, two labels that are distinct can be processed into the same parameterized string.
 
-### Example
+### Example of "labels are too similar" error
 
 ```yaml
 name: "Bug report"
@@ -254,7 +254,7 @@ body:
 
 When a `checkboxes` element is present, each of its nested labels must be unique among its peers, as well as among other input types.
 
-### Example
+### Example of "checkboxes must have unique labels" error
 
 ```yaml
 name: "Bug report"
@@ -305,7 +305,7 @@ Each body block must contain the key `type`.
 
 Errors with `body` will be prefixed with `body[i]` where `i` represents the zero-indexed index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
 
-### Example
+### Example of "body[i]: required key type is missing" error
 
 ```yaml
 body:
@@ -328,7 +328,7 @@ One of the body blocks contains a type value that is not one of the [permitted t
 
 Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
 
-### Example
+### Example of "body[i]: `x` is not a valid input type" error
 
 ```yaml
 body:
@@ -352,7 +352,7 @@ One of the required `value` attributes has not been provided. The error occurs w
 
 Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
 
-### Example
+### Example of "body[i]: required attribute key `value` is missing" error
 
 ```yaml
 body:
@@ -380,7 +380,7 @@ Within its `attributes` block, a value has the wrong data type.
 
 Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
 
-### Example
+### Example of "body[i]: label must be a string" error
 
 The `label` below is being parsed as a Boolean, but it should be a string.
 
@@ -429,7 +429,7 @@ body:
 
 Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
 
-### Example
+### Example of "body[i]: `id` can only contain numbers, letters, -, _" error
 
 ```yaml
 name: "Bug report"
@@ -457,7 +457,7 @@ An unexpected key, `x`, was provided at the same indentation level as `type` and
 
 Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
 
-### Example
+### Example of "body[i]: `x` is not a permitted key" error
 
 ```yaml
 body:
@@ -482,7 +482,7 @@ To minimize the risk of private information and credentials being posted publicl
 
 Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
 
-### Example
+### Example of "body[i]: `label` contains forbidden word" error
 
 ```yaml
 body:
@@ -512,7 +512,7 @@ An invalid key has been supplied in an `attributes` block.
 
 Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
 
-### Example
+### Example of "body[i]: `x` is not a permitted attribute" error
 
 ```yaml
 body:
@@ -537,7 +537,7 @@ For checkboxes and dropdown input types, the choices defined in the `options` ar
 
 Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
 
-### Example
+### Example of "body[i]: `options` must be unique" error
 
 ```yaml
 body:
@@ -568,7 +568,7 @@ body:
 
 Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
 
-### Example
+### Example of "body[i]: `options` must not include the reserved word, none" error
 
 ```yaml
 body:
@@ -603,7 +603,7 @@ There are a number of English words that become processed into Boolean values by
 
 Errors with `body` will be prefixed with `body[i]` where `i` represents the index of the body block containing the error. For example, `body[0]` tells us that the error has been caused by the first block in the `body` list.
 
-### Example
+### Example of "body[i]: `options` must not include booleans. Please wrap values such as 'yes', and 'true' in quotes" error
 
 ```yaml
 body:
@@ -635,7 +635,7 @@ The template body `key:value` pair can not be empty. For more information about
 
 The error can be fixed by adding the `body:` section.
 
-### Example
+### Example of "body cannot be empty" error
 
 ```yaml
 name: Support Request