diff --git a/source/content/guides/wordpress-configurations/07-wordpress-font-library.md b/source/content/guides/wordpress-configurations/07-wordpress-font-library.md
index aaf195ce3d..5d648a6588 100644
--- a/source/content/guides/wordpress-configurations/07-wordpress-font-library.md
+++ b/source/content/guides/wordpress-configurations/07-wordpress-font-library.md
@@ -18,7 +18,7 @@ This section provides information on how to use the WordPress Font Library on Pa
 
 WordPress 6.5 introduces a new [Font Library](https://make.wordpress.org/core/2024/03/14/new-feature-font-library/) feature. The Font Library allows you to upload fonts from your computer or add any of the fonts available on Google's font library to your WordPress site. In anticipation of this, Pantheon has added a feature to our [Pantheon MU Plugin](https://github.com/pantheon-systems/pantheon-mu-plugin) to store those fonts in a writeable directory (`wp-content/uploads/fonts/`), so that you can use the feature without any issues after updating your sites to 6.5. 
 
-By default, WordPress will install fonts into `wp-content/fonts/` if it is writeable. If `wp-content/fonts/` is not writeable, like on Pantheon environments, WordPress will install fonts into `wp-content/uploads/fonts/`. This can create inconsistency if WordPress is using its default behavior because your `wp-content/fonts/` is likely to be writeable on your local environment. In this instance, fonts installed _on Pantheon_ would be stored in `wp-content/uploads/fonts` but fonts installed _locally_ would be stored in `wp-content/fonts`, which is why we have altered the behavior in the mu-plugin.
+By default, WordPress will install fonts into `wp-content/fonts/` if it is writeable. If `wp-content/fonts/` is not writeable, like on Pantheon environments, WordPress will install fonts into `wp-content/uploads/fonts/`. This can create inconsistency when developing locally if WordPress is using its default behavior because your `wp-content/fonts/` is likely to be writeable on your local environment. In this instance, fonts installed _on Pantheon_ would be stored in `wp-content/uploads/fonts` but fonts installed _locally_ would be stored in `wp-content/fonts`, which is why we have altered the behavior in the mu-plugin.
 
 ## Using the `font_dir` Filter
 
diff --git a/source/releasenotes/2024-03-11-pantheon-advanced-page-cache-1.5.0.md b/source/releasenotes/2024-03-11-pantheon-advanced-page-cache-1.5.0.md
index 1fb021082c..f931b04caa 100644
--- a/source/releasenotes/2024-03-11-pantheon-advanced-page-cache-1.5.0.md
+++ b/source/releasenotes/2024-03-11-pantheon-advanced-page-cache-1.5.0.md
@@ -1,7 +1,7 @@
 ---
 title: Enhancements in Pantheon Advanced Page Cache v1.5.0
 published_date: "2024-03-11"
-categories: [wordpress, plugins]
+categories: [wordpress,plugins]
 ---
 
 Pantheon Advanced Page Cache v1.5.0 is now available on [WordPress.org](https://wordpress.org/plugins/pantheon-advanced-page-cache/) and [GitHub](https://github.com/pantheon-systems/pantheon-advanced-page-cache/releases/tag/1.5.0). This release adds a new filter to make cache purges less aggressive and provide more flexibility for developers and the sites they maintain. You can learn about the filter in the plugin's [README file](https://github.com/pantheon-systems/pantheon-advanced-page-cache?tab=readme-ov-file#ignoring-specific-post-types) which includes an example of how to use it.