github · schalkneethling · Jan 6, 2023 · Jan 6, 2023 · Jan 6, 2023 · Jan 6, 2023
diff --git a/...despaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md b/...despaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md
@@ -1,9 +1,9 @@
 ---
 title: Troubleshooting creation and deletion of codespaces
-intro: 'This article provides troubleshooting steps for common issues you may experience when creating or deleting a codespace, including storage and configuration issues.'
+intro: "This article provides troubleshooting steps for common issues you may experience when creating or deleting a codespace, including storage and configuration issues."
 versions:
-  fpt: '*'
-  ghec: '*'
+  fpt: "*"
+  ghec: "*"
 type: reference
 topics:
   - Codespaces
@@ -13,6 +13,7 @@ shortTitle: Creation and deletion
 ## Creating codespaces
 
 ### No access to create a codespace
+
 {% data variables.product.prodname_github_codespaces %} is not available for all repositories. If the options for creating a codespace are not displayed, {% data variables.product.prodname_github_codespaces %} may not be available for that repository. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#access-to-codespaces)."
 
 Provided you have remaining monthly included usage of {% data variables.product.prodname_github_codespaces %} on your personal account, or you have set up a payment method and a spending limit, you will be able to create codespaces for public repositories. However, you can only create a codespace for a private repository if you can push changes to the repository, or you can fork the repository.
@@ -31,7 +32,7 @@ If you still cannot create a codespace for a repository where {% data variables.
 
 ### Codespace creation fails
 
-If the creation of a codespace fails, it's likely to be due to a temporary infrastructure issue in the cloud - for example, a problem provisioning a virtual machine for the codespace. A less common reason for failure is if it takes longer than an hour to build the container. In this case, the build is cancelled and codespace creation will fail.
+If the creation of a codespace fails, it's likely to be due to a temporary infrastructure issue in the cloud - for example, a problem provisioning a virtual machine for the codespace. A less common reason for failure is if it takes longer than an hour to build the container. In this case, the build is canceled and codespace creation will fail.
 
 {% note %}
 
@@ -50,23 +51,26 @@ If you create a codespace and the creation fails:
    {% note %}
 
    **Note**: To view the logs during a build:
-   * In the browser, click **View logs.** 
+
+   - In the browser, click **View logs.**
 
    ![Screenshot of the Codespaces web UI with the View logs link emphasized](/assets/images/help/codespaces/web-ui-view-logs.png)
 
-   * In the VS Code desktop application, click **Building codespace** in the "Setting up remote connection" that's displayed. 
+   - In the VS Code desktop application, click **Building codespace** in the "Setting up remote connection" that's displayed.
 
    ![Screenshot of VS Code with the Building codespace link emphasized](/assets/images/help/codespaces/vs-code-building-codespace.png)
 
-    {% endnote %}
-2. If you have a container that takes a long time to build, consider using prebuilds to speed up codespace creations. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)."
+   {% endnote %}
+
+1. If you have a container that takes a long time to build, consider using prebuilds to speed up codespace creations. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)."
 
 ## Deleting codespaces
 
 A codespace can only be deleted by:
-* The person who created the codespace.
-* An organization owner for an organization-owned codespace.
-* Automatic deletion at the end of a retention period. 
+
+- The person who created the codespace.
+- An organization owner for an organization-owned codespace.
+- Automatic deletion at the end of a retention period.
 
 For more information, see "[Deleting a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace)" and "[Configuring automatic deletion of your codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)."
 
@@ -91,6 +95,7 @@ Some more destructive options:
 ```
 This codespace is currently running in recovery mode due to a container error.
 ```
+
 Review the creation logs and update the dev container configuration as needed. For more information, see "[{% data variables.product.prodname_github_codespaces %} logs](/codespaces/troubleshooting/github-codespaces-logs)."
 
 You can then try restarting the codespace, or rebuilding the container. For more information on rebuilding the container, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace)."
diff --git a/...ies/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md b/...ies/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
@@ -5,8 +5,8 @@ redirect_from:
   - /articles/blocking-a-user-from-your-organization
   - /github/building-a-strong-community/blocking-a-user-from-your-organization
 versions:
-  fpt: '*'
-  ghec: '*'
+  fpt: "*"
+  ghec: "*"
 topics:
   - Community
 shortTitle: Block from your org
@@ -23,18 +23,21 @@ You can block non-members from within your organization's settings or from a spe
 {% endtip %}
 
 At the time that you block a user from your organization:
+
 - The user stops watching your organization's repositories
 - The user's stars and issue assignments are removed from your repositories
 - The user's votes on discussions or comments in your organization's repositories are deleted
 - The user is removed as a collaborator on your organization's repositories
 - The user's contributions to your organization's repositories are no longer counted as contributions for them
-- Any pending repository or organization invitations to the blocked user are cancelled
+- Any pending repository or organization invitations to the blocked user are canceled
 
 After you've blocked a user from your organization, they cannot:
+
 - Cross-reference your organization's repositories in comments
 - Fork, watch, pin, or star your organization's repositories
 
 In your organization's repositories, blocked users also cannot:
+
 - Open issues
 - Send, close, or merge pull requests
 - Comment on issues, pull requests, or commits
@@ -44,28 +47,25 @@ In your organization's repositories, blocked users also cannot:
 
 1. Navigate to the comment whose author you would like to block.
 2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Block user**.
-![The horizontal kebab icon and comment moderation menu showing the block user option](/assets/images/help/repository/comment-menu-block-user.png)
+   ![The horizontal kebab icon and comment moderation menu showing the block user option](/assets/images/help/repository/comment-menu-block-user.png)
 3. If you'd like to set a time limit for the block, use the Block user drop-down menu, and select the amount of time you'd like to block the user.
-![Block time limit in the block user drop-down menu](/assets/images/help/organizations/org-block-options-menu-from-comment.png)
+   ![Block time limit in the block user drop-down menu](/assets/images/help/organizations/org-block-options-menu-from-comment.png)
 4. If you'd like to hide all of the comments the user has made in the organization, select **Hide this user's comments** and choose a reason.
-![Send a notification in the block user drop-down menu](/assets/images/help/organizations/org-block-options-menu-hide-user-comments.png)
+   ![Send a notification in the block user drop-down menu](/assets/images/help/organizations/org-block-options-menu-hide-user-comments.png)
 5. If you'd like to notify the user why they're being blocked, select **Send a notification to this user**.
-![Send a notification in the block user drop-down menu](/assets/images/help/organizations/org-block-options-menu-send-notification.png)
+   ![Send a notification in the block user drop-down menu](/assets/images/help/organizations/org-block-options-menu-send-notification.png)
 6. To block the user, click **Block user from organization** or **Block user from organization and send message**.
-![Block user button](/assets/images/help/organizations/org-block-user-button-in-comment.png)
+   ![Block user button](/assets/images/help/organizations/org-block-user-button-in-comment.png)
 
 ## Blocking a user in the organization settings
 
 1. To block an organization member, first [remove the user](/articles/removing-a-member-from-your-organization) from the organization.
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-{% data reusables.organizations.block_users %}
-6. Under "Block a user", type the username of the user you'd like to block.
-![Username field](/assets/images/help/organizations/org-block-username-field.png)
-7. If you'd like to set a time limit for the block, use the Block options drop-down menu, and select the amount of time you'd like to block the user.
-![Block options drop-down menu](/assets/images/help/organizations/org-block-options-menu.png)
-8. Click **Block user**.
+{% data reusables.organizations.block_users %} 6. Under "Block a user", type the username of the user you'd like to block.
+![Username field](/assets/images/help/organizations/org-block-username-field.png) 7. If you'd like to set a time limit for the block, use the Block options drop-down menu, and select the amount of time you'd like to block the user.
+![Block options drop-down menu](/assets/images/help/organizations/org-block-options-menu.png) 8. Click **Block user**.
 ![Block button](/assets/images/help/organizations/org-block-user-button.png)
 
 ## Further reading

diff --git a/...maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md b/...maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md
@@ -1,12 +1,12 @@
 ---
 title: Blocking a user from your personal account
-intro: 'You can block a user to deny them access to your activity and repositories, and to prevent them from sending you notifications.'
+intro: "You can block a user to deny them access to your activity and repositories, and to prevent them from sending you notifications."
 redirect_from:
   - /articles/blocking-a-user-from-your-personal-account
   - /github/building-a-strong-community/blocking-a-user-from-your-personal-account
 versions:
-  fpt: '*'
-  ghec: '*'
+  fpt: "*"
+  ghec: "*"
 topics:
   - Community
 shortTitle: Block from your account
@@ -23,6 +23,7 @@ You can block a user in your account settings or from the user's profile. {% dat
 {% endtip %}
 
 When you block a user:
+
 - The user stops following you
 - The user stops watching and unpins your repositories
 - The user is not able to join any organizations you are an owner of
@@ -32,12 +33,13 @@ When you block a user:
 - The user's contributions to your repositories are no longer counted as contributions for them
 - Your contributions to the blocked user's repositories are no longer counted as contributions for you
 - You are removed as a collaborator on their repositories
-- Their sponsorship of you is cancelled
-- Any pending repository or account successor invitations to or from the blocked user are cancelled
+- Their sponsorship of you is canceled
+- Any pending repository or account successor invitations to or from the blocked user are canceled
 - The user is removed as a collaborator from all the projects and {% data variables.projects.projects_v1_boards %} owned by you
 - You are removed as a collaborator from all the projects and {% data variables.projects.projects_v1_boards %} owned by the user
 
 After you've blocked a user, they cannot:
+
 - Send you any notifications, including by [@mentioning](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) your username
 - Comment on or edit issues or pull requests that you've created
 - React to your comments on issues, pull requests, and commits
@@ -52,6 +54,7 @@ After you've blocked a user, they cannot:
 - Make changes to your public projects and {% data variables.projects.projects_v1_boards %}
 
 In repositories you own, blocked users also cannot:
+
 - Open issues
 - Send, close, or merge pull requests
 - Comment on issues, pull requests, or commits
@@ -60,18 +63,15 @@ In repositories you own, blocked users also cannot:
 ## Blocking a user in your account settings
 
 {% data reusables.user-settings.access_settings %}
-{% data reusables.user-settings.blocked_users %}
-3. Under "Block a user", type the username of the user you'd like to block, then click **Block user**.
-  ![Username field and block button](/assets/images/help/settings/user-settings-block-user.png)
-4. Optionally, to display a warning when you visit a repository where a blocked user is a contributor, select **Warn me when a blocked user is a prior contributor to a repository**.
-  ![Warn about blocked users option](/assets/images/help/settings/warn-block-user.png)
+{% data reusables.user-settings.blocked_users %} 3. Under "Block a user", type the username of the user you'd like to block, then click **Block user**.
+![Username field and block button](/assets/images/help/settings/user-settings-block-user.png) 4. Optionally, to display a warning when you visit a repository where a blocked user is a contributor, select **Warn me when a blocked user is a prior contributor to a repository**.
+![Warn about blocked users option](/assets/images/help/settings/warn-block-user.png)
 
 ## Blocking a user from their profile page
 
 {% data reusables.profile.user_profile_page_navigation %}
-{% data reusables.profile.user_profile_page_block_or_report %}
-3. Click **Block user**.
-   ![Modal box with options to block user or report abuse](/assets/images/help/profile/profile-blockuser.png)
+{% data reusables.profile.user_profile_page_block_or_report %} 3. Click **Block user**.
+![Modal box with options to block user or report abuse](/assets/images/help/profile/profile-blockuser.png)
 
 {% note %}
 

diff --git a/...tplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md b/...tplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md
@@ -1,19 +1,20 @@
 ---
 title: Viewing metrics for your listing
-intro: 'The {% data variables.product.prodname_marketplace %} Insights page displays metrics for your {% data variables.product.prodname_github_app %}. You can use the metrics to track your {% data variables.product.prodname_github_app %}''s performance and make more informed decisions about pricing, plans, free trials, and how to visualize the effects of marketing campaigns.'
+intro: "The {% data variables.product.prodname_marketplace %} Insights page displays metrics for your {% data variables.product.prodname_github_app %}. You can use the metrics to track your {% data variables.product.prodname_github_app %}'s performance and make more informed decisions about pricing, plans, free trials, and how to visualize the effects of marketing campaigns."
 redirect_from:
   - /apps/marketplace/managing-github-marketplace-listings/viewing-performance-metrics-for-a-github-marketplace-listing
   - /apps/marketplace/viewing-performance-metrics-for-a-github-marketplace-listing
   - /apps/marketplace/github-marketplace-insights
   - /marketplace/github-marketplace-insights
   - /developers/github-marketplace/viewing-metrics-for-your-listing
 versions:
-  fpt: '*'
-  ghec: '*'
+  fpt: "*"
+  ghec: "*"
 topics:
   - Marketplace
 shortTitle: View listing metrics
 ---
+
 You can view metrics for the past day (24 hours), week, month, or for the entire duration of time that your {% data variables.product.prodname_github_app %} has been listed.
 
 {% note %}
@@ -26,31 +27,28 @@ You can view metrics for the past day (24 hours), week, month, or for the entire
 
 The Insights page displays these performance metrics, for the selected time period:
 
-* **Subscription value:** Total possible revenue (in US dollars) for subscriptions. This value represents the possible revenue if no plans or free trials are cancelled and all credit transactions are successful. The subscription value includes the full value for plans that begin with a free trial in the selected time period, even when there are no financial transactions in that time period. The subscription value also includes the full value of upgraded plans in the selected time period but does not include the prorated amount. To see and download individual transactions, see "[GitHub Marketplace transactions](/marketplace/github-marketplace-transactions/)."
-* **Visitors:** Number of people that have viewed a page in your GitHub Apps listing. This number includes both logged in and logged out visitors.
-* **Pageviews:** Number of views the pages in your GitHub App's listing received. A single visitor can generate more than one page view.
+- **Subscription value:** Total possible revenue (in US dollars) for subscriptions. This value represents the possible revenue if no plans or free trials are canceled and all credit transactions are successful. The subscription value includes the full value for plans that begin with a free trial in the selected time period, even when there are no financial transactions in that time period. The subscription value also includes the full value of upgraded plans in the selected time period but does not include the prorated amount. To see and download individual transactions, see "[GitHub Marketplace transactions](/marketplace/github-marketplace-transactions/)."
+- **Visitors:** Number of people that have viewed a page in your GitHub Apps listing. This number includes both logged in and logged out visitors.
+- **Pageviews:** Number of views the pages in your GitHub App's listing received. A single visitor can generate more than one page view.
 
 {% note %}
 
-**Note:**  Your estimated subscription value could be much higher than the transactions processed for this period. 
+**Note:** Your estimated subscription value could be much higher than the transactions processed for this period.
 
 {% endnote %}
 
 ### Conversion performance
 
-* **Unique visitors to landing page:** Number of people who viewed your GitHub App's landing page.
-* **Unique visitors to checkout page:** Number of people who viewed one of your GitHub App's checkout pages.
-* **Checkout page to new subscriptions:** Total number of paid subscriptions, free trials, and free subscriptions. See the "Breakdown of total subscriptions" for the specific number of each type of subscription.
+- **Unique visitors to landing page:** Number of people who viewed your GitHub App's landing page.
+- **Unique visitors to checkout page:** Number of people who viewed one of your GitHub App's checkout pages.
+- **Checkout page to new subscriptions:** Total number of paid subscriptions, free trials, and free subscriptions. See the "Breakdown of total subscriptions" for the specific number of each type of subscription.
 
 ![Marketplace insights](/assets/images/marketplace/marketplace_insights.png)
 
 To access {% data variables.product.prodname_marketplace %} Insights:
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.developer_settings %}
-{% data reusables.user-settings.marketplace_apps %}
-4. Select the {% data variables.product.prodname_github_app %} that you'd like to view Insights for.
-{% data reusables.user-settings.edit_marketplace_listing %}
-6. Click the **Insights** tab.
-7. Optionally, select a different time period by clicking the Period dropdown in the upper-right corner of the Insights page.
+{% data reusables.user-settings.marketplace_apps %} 4. Select the {% data variables.product.prodname_github_app %} that you'd like to view Insights for.
+{% data reusables.user-settings.edit_marketplace_listing %} 6. Click the **Insights** tab. 7. Optionally, select a different time period by clicking the Period dropdown in the upper-right corner of the Insights page.
 ![Marketplace time period](/assets/images/marketplace/marketplace_insights_time_period.png)