Merge pull request github#19584 from github/repo-sync

Octomerger · web-flow · commit 435af29cbc5f · 2021-05-27T11:31:14.000+10:00
repo sync
diff --git a/content/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch.md b/content/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch.md
@@ -18,7 +18,7 @@ When you rename a branch on {% data variables.product.product_location %}, any U
 
 Although file URLs are automatically redirected, raw file URLs are not redirected. Also, {% data variables.product.prodname_dotcom %} does not perform any redirects if users perform a `git pull` for the previous branch name.
 
-{% data variables.product.prodname_actions %} workflows do not follow renames, so if your repository publishes an action, anyone using that action with `@{old-branch-name}` will break. You should consider adding a new branch with the original content plus an additional commit reporting that the banch name is deprecated and suggesting that users migrate to the new branch name.
+{% data variables.product.prodname_actions %} workflows do not follow renames, so if your repository publishes an action, anyone using that action with `@{old-branch-name}` will break. You should consider adding a new branch with the original content plus an additional commit reporting that the branch name is deprecated and suggesting that users migrate to the new branch name.
 
 ### Renaming a branch
 
diff --git a/content/github/writing-on-github/index.md b/content/github/writing-on-github/index.md
@@ -5,6 +5,7 @@ redirect_from:
   - /articles/github-flavored-markdown/
   - /articles/writing-on-github/
   - /categories/writing-on-github
+intro: 'You can structure the information shared on {% data variables.product.product_name %} with various formatting options.'
 versions:
   free-pro-team: '*'
   enterprise-server: '*'
@@ -15,4 +16,3 @@ children:
   - /working-with-saved-replies
   - /editing-and-sharing-content-with-gists
 ---
-
