diff --git a/src/protocols/validate/forward-violations.md b/src/protocols/validate/forward-violations.md
index 591ecff8dd..78341d8747 100644
--- a/src/protocols/validate/forward-violations.md
+++ b/src/protocols/validate/forward-violations.md
@@ -51,5 +51,5 @@ Violations are sent to the selected Source as `analytics.track()` calls. The cal
 > info ""
 > Enabling Violation forwarding generates 1 additional MTU in your workspace. If you are on an API billing plan, you are charged for the increased API volume generated by the forwarded violations.
 
-> warning "`Violation Generated` events"
+> warning "Violation Generated events"
 > `Violation Generated` events do not appear in the source's Schema tab, but they do appear as Violation Generated events in the [debugger](/docs/connections/sources/debugger/).
diff --git a/src/segment-app/iam/restrict-access.md b/src/segment-app/iam/restrict-access.md
index 89c4b7d721..c87d08dbe3 100644
--- a/src/segment-app/iam/restrict-access.md
+++ b/src/segment-app/iam/restrict-access.md
@@ -13,7 +13,7 @@ All team members on an account have access to make changes anywhere in the works
 
 ## Business Tier Only — Permission Levels
 
-At present, Business Tier workspaces can have **Owners,** **Read-Only Members,** and **Source Collaborators. **
+At present, Business Tier workspaces can have **Owners,** **Read-Only Members,** and **Source Collaborators.**
 
 **Workspace Owners** have full access to the workspace with the ability to view and update settings and create, view, update, and delete sub-resources like Sources and Destinations.