Merge pull request #238 from justwriteclick/build

Fix missing images; label CODEOWNERS file examples

Author: annegentle

_learn/12-ssg-performance.md

@@ -3,7 +3,7 @@ title: "Static Site Generator performance considerations"
 layout: learn
 image:
   path: /images/learn/ssg-performance.png
-  thumbnail: /images/learn/ssg-performance-400×225.png
+  thumbnail: /images/learn/ssg-performance-400x225.png
 ---
 
 When you start building large documentation sites, or gluing together multiple documentation sets, you might look for performance gains in the build time. Having smaller doc sites helps with this, so that you can build with your static site generator systems in parallel, but also look for incremental builds or ways to measure build times to look for areas where the build is slowed down and then find a root cause for the slower performance.

_posts/articles/2023-10-01-protecting-codeowners-file.md

@@ -21,6 +21,7 @@ A `CODEOWNERS` file can be stored in a directory, or in the `.github` folder, wh
 
 A straightforward example involves protecting the `docs` folder in the `main` branch, where the `main` branch is the branch used to publish the documentation. In this example, the org name is `justwriteclick` and the username is `annegentle`. You would name the file `CODEOWNERS` and store it in a `docs` directory.
 
+Example `CODEOWNERS` file:
 ```
 @justwriteclick/annegentle
 ```
@@ -31,8 +32,9 @@ Then, make sure that the branch is protected using the repository's **Setting**
 
 <img src="../../images/branch-protection-rule.png" alt="GitHub Branch protection rules settings.">
 
-To see an example of this setup, look at the Microsoft 365 community documentation repository at https://github.com/MicrosoftDocs/microsoft-365-community/. The `CODEOWNERS` file contains a team name, `@microsoftdocs/officedocs-admin`, and those team members can review and merge the list of documents in the `CODEOWNERS` file. The documents contain configuration information as well as the `CODEOWNERS` file itself. 
+To see an example of this setup, look at the Microsoft 365 community documentation repository at [https://github.com/MicrosoftDocs/microsoft-365-community/](https://github.com/MicrosoftDocs/microsoft-365-community/). The `CODEOWNERS` file contains a team name, `@microsoftdocs/officedocs-admin`, and those team members can review and merge the list of documents in the `CODEOWNERS` file. The documents contain configuration information as well as the `CODEOWNERS` file itself. 
 
+Example `CODEOWNERS` file from MicrosoftDocs:
 ```
 docfx.json                          @microsoftdocs/officedocs-admin
 .openpublishing.build.ps1           @microsoftdocs/officedocs-admin