diff --git a/_data/toc.yaml b/_data/toc.yaml
index 12609e91b4..5b43a1594f 100644
--- a/_data/toc.yaml
+++ b/_data/toc.yaml
@@ -1811,7 +1811,7 @@ contribute:
     - path: /contribute/components/badges/
       title: Badges
     - path: /contribute/components/call-outs/
-      title: Call outs
+      title: Callouts
     - path: /contribute/components/cards/
       title: Cards
     - path: /contribute/components/code-blocks/
diff --git a/contribute/components/call-outs.md b/contribute/components/call-outs.md
index 4210a2ad73..e7f8bcd3cb 100644
--- a/contribute/components/call-outs.md
+++ b/contribute/components/call-outs.md
@@ -1,10 +1,10 @@
 ---
 description: components and formatting examples used in Docker's docs
-title: Call outs
+title: Callouts
 toc_max: 3
 ---
 
-We support these broad categories of call outs:
+We support these broad categories of callouts:
 
 - Notes (no Liquid tag required)
 - Important, which use the `{: .important}` tag
@@ -37,21 +37,21 @@ We support these broad categories of call outs:
 > `docker-compose down`. If you want to remove the volumes, you will need to add
 > the `--volumes` flag.
 >
-> The Docker Dashboard does _not_ remove volumes when you delete the app stack.
+> The Docker Dashboard does not remove volumes when you delete the app stack.
 {: .warning}
 
 ## HTML
 
 ```html
 > **Note**
-  >
-  > Note the way the `get_hit_count` function is written. This basic retry
-  > loop lets us attempt our request multiple times if the redis service is
-  > not available. This is useful at startup while the application comes
-  > online, but also makes our application more resilient if the Redis
-  > service needs to be restarted anytime during the app's lifetime. In a
-  > cluster, this also helps handling momentary connection drops between
-  > nodes.
+>
+> Note the way the `get_hit_count` function is written. This basic retry
+> loop lets us attempt our request multiple times if the redis service is
+> not available. This is useful at startup while the application comes
+> online, but also makes our application more resilient if the Redis
+> service needs to be restarted anytime during the app's lifetime. In a
+> cluster, this also helps handling momentary connection drops between
+> nodes.
 
 > **Important**
 >
diff --git a/contribute/overview.md b/contribute/overview.md
index a17adadff5..3ec41f1af3 100644
--- a/contribute/overview.md
+++ b/contribute/overview.md
@@ -25,8 +25,8 @@ as possible for you to work in this repository. The following sections guide you
             <div class="component-icon">
                  <img src="/assets/images/menu-book.svg" alt="Docker Desktop for Mac" width="45" height="45">
             </div>
-                <h2 id="docker-for-mac"><a href="/contribute/style/grammar/">Grammar guide</a></h2>
-                <p>Explore Docker's grammar guide.</p>
+                <h2 id="docker-for-mac"><a href="/contribute/style/grammar/">Grammar and style</a></h2>
+                <p>Explore Docker's grammar and style guide.</p>
          </div>
      </div>
      <div class="col-xs-12 col-sm-12 col-md-12 col-lg-4 block">
@@ -34,7 +34,7 @@ as possible for you to work in this repository. The following sections guide you
             <div class="component-icon">
                 <img src="/assets/images/newspaper.svg" alt="Docker for Linux" width="45" height="45">
             </div>
-                <h2 id="docker-for-linux"><a href="/contribute/style/formatting/">Formatting guidelines</a></h2>
+                <h2 id="docker-for-linux"><a href="/contribute/style/formatting/">Formatting</a></h2>
                 <p>Format your content to match the rest of our documentation.</p>
         </div>
     </div>