diff --git a/coaching/roster/flags-and-groups.mdx b/coaching/roster/flags-and-groups.mdx
index a1384d9..df5d8f9 100644
--- a/coaching/roster/flags-and-groups.mdx
+++ b/coaching/roster/flags-and-groups.mdx
@@ -39,7 +39,7 @@ You can tune these cutoffs. An alert rule can also carry its threshold at a give
 
 Group athletes however you coach: by squad, by event, by training block such as "70.3 Build". Build and edit groups from the group manager on your [roster](https://coach.saturday.fit/dashboard). A group lets you act on many athletes in one move, message everyone at once, and scope alert rules to that group.
 
-A group is **manual**, where you pick the athletes, or **smart**, where you set rules on sport, fitness level, last activity, subscription, sex, or age range and membership updates as your roster changes. A smart group can also force specific athletes in or out regardless of the rules.
+A group is **manual**, where you pick the athletes, or **smart**, where you set rules on sport, fitness level, last activity, subscription, sex, or age range and membership updates as your roster changes.
 
 Org admins on Head Coach and above get a second, governance-oriented view at [Control panel, Groups](https://coach.saturday.fit/admin/groups): the whole org group tree, assigning an org group to an assistant coach, promoting a personal group so the org can share it, and a read-only view of who sees what. Day-to-day grouping still happens on the roster.
 
diff --git a/guides/oauth2.mdx b/guides/oauth2.mdx
index f9ffc2b..3a7a91b 100644
--- a/guides/oauth2.mdx
+++ b/guides/oauth2.mdx
@@ -251,7 +251,7 @@ const newTokens = await response.json();
 | `ai:chat` | AI Coach conversations |
 | `offline_access` | Be issued a refresh token, and use it |
 
-`offline_access` grants no data access by itself. It is the OIDC and MCP signal that you want to stay connected without sending the athlete back through consent every hour. Request it alongside your data scopes if you need refresh, and note that it is not included in the default `athlete:read` fallback.
+`offline_access` grants no data access by itself. It is the OIDC and MCP signal that you want to stay connected without sending the athlete back through consent every hour. Request it alongside your data scopes if you need refresh. It is not included in the default `athlete:read` fallback.
 
 `ai:chat` is available to pre-registered clients only. It is deliberately excluded from the scopes advertised in discovery metadata, so a client registering through a Client ID Metadata Document cannot request it.