diff --git a/style-guide/content-strategy.md b/style-guide/content-strategy.md
index 6e606d3ef..6e9300ac3 100644
--- a/style-guide/content-strategy.md
+++ b/style-guide/content-strategy.md
@@ -15,7 +15,7 @@
 
 - Put new pages in the nav group that matches the user journey.
 - Filenames use kebab-case, such as `custom-domain.mdx`.
-- Order content by how often readers need it, most common tasks come first.
+- Order content by how often readers need it; most common tasks come first.
 - The help center is for agent-written content that answers specific user questions from conversations with support or the assistant.
 - Guides are end-to-end tutorials and best practices for concepts adjacent to Mintlify but not part of the platform itself. Like Git best practices or integrating Mintlify CLI commands into your CI pipeline.
 
diff --git a/style-guide/formatting-and-components.md b/style-guide/formatting-and-components.md
index 94b7c82b5..c8513d832 100644
--- a/style-guide/formatting-and-components.md
+++ b/style-guide/formatting-and-components.md
@@ -5,7 +5,7 @@ Google's defaults apply: [headings](https://developers.google.com/style/headings
 ## Frontmatter
 
 - Every page needs `title`, `description`, and `keywords`.
-  - Titles use sentence case
+  - Titles use sentence case.
   - Descriptions populate search results, so they must help readers determine if a page will solve the task they're working on.
   - Keywords are used to improve search. Any words in the title are already keywords.
 - Optional: `sidebarTitle` when the title is too long for the sidebar.