diff --git a/modules/subscriptions/pages/astream-subscriptions-exclusive.adoc b/modules/subscriptions/pages/astream-subscriptions-exclusive.adoc
index 5e98ef6..7dbb782 100644
--- a/modules/subscriptions/pages/astream-subscriptions-exclusive.adoc
+++ b/modules/subscriptions/pages/astream-subscriptions-exclusive.adoc
@@ -73,7 +73,7 @@ Exception in thread "main" java.lang.IllegalStateException: Cannot connect to pu
 Caused by: org.apache.pulsar.client.api.PulsarClientException$ConsumerBusyException: {"errorMsg":"Exclusive consumer is already connected","reqId":2964994443801550457, "remote":"<service_url>", "local":"/192.168.0.95:55777"}
 ----
 
-The second consumer can't subscribe to the topic because the subscription is *exclusive*. +
+The second consumer cannot subscribe to the topic because the subscription is *exclusive*. +
 
 In the example above, the consumer didn't declare a subscription type, so {pulsar-short} created an exclusive subscription by default. +
 To explicitly define an exclusive subscription, add `.subscriptionType(SubscriptionType.Exclusive)` to the consumer.
diff --git a/modules/subscriptions/pages/astream-subscriptions-keyshared.adoc b/modules/subscriptions/pages/astream-subscriptions-keyshared.adoc
index 41be49b..c40fe07 100644
--- a/modules/subscriptions/pages/astream-subscriptions-keyshared.adoc
+++ b/modules/subscriptions/pages/astream-subscriptions-keyshared.adoc
@@ -126,7 +126,7 @@ Caused by: org.apache.pulsar.client.api.PulsarClientException$ConsumerAssignExce
 	at com.datastax.pulsar.SimplePulsarConsumer.main(SimplePulsarConsumer.java:47)
 ----
 
-The new consumer can't subscribe to the topic because you reserved the entire hash range for the first consumer.
+The new consumer cannot subscribe to the topic because you reserved the entire hash range for the first consumer.
 
 == Key_Shared subscription video
 
diff --git a/modules/subscriptions/pages/astream-subscriptions-shared.adoc b/modules/subscriptions/pages/astream-subscriptions-shared.adoc
index 0da4026..aec8d20 100644
--- a/modules/subscriptions/pages/astream-subscriptions-shared.adoc
+++ b/modules/subscriptions/pages/astream-subscriptions-shared.adoc
@@ -70,7 +70,7 @@ The confirmation message and a cursor appear to indicate the consumer is ready.
 
 . Open as many terminals as you'd like and run `SimplePulsarConsumer.java`. All the consumers subscribe to the topic and consume messages in a round-robin fashion. 
 
-If you run this test with xref:astream-subscriptions-exclusive.adoc[exclusive subscriptions], you can't attach more than once subscriber to the exclusive topic.
+If you run this test with xref:astream-subscriptions-exclusive.adoc[exclusive subscriptions], you cannot attach more than once subscriber to the exclusive topic.
 Since this test uses shared subscriptions, you can attach multiple consumers to the topic.
 
 == Shared subscription video
diff --git a/modules/use-cases-architectures/pages/change-data-capture/questions-and-patterns.adoc b/modules/use-cases-architectures/pages/change-data-capture/questions-and-patterns.adoc
index 9be869d..3386602 100644
--- a/modules/use-cases-architectures/pages/change-data-capture/questions-and-patterns.adoc
+++ b/modules/use-cases-architectures/pages/change-data-capture/questions-and-patterns.adoc
@@ -63,7 +63,7 @@ For more, see the https://docs.datastax.com/en/cdc-for-cassandra/docs/latest/ins
 .Does the {cass-short} Source Connector use a dead-letter topic?
 [%collapsible]
 ====
-A dead letter topic is used when a message can't be delivered to a consumer. Maybe the message acknowledgment time expired (no consumer acknowledged receipt of the message), or a consumer negatively acknowledged the message, or a retry letter topic is in use and retries were exhausted.
+A dead letter topic is used when a message cannot be delivered to a consumer. Maybe the message acknowledgment time expired (no consumer acknowledged receipt of the message), or a consumer negatively acknowledged the message, or a retry letter topic is in use and retries were exhausted.
 
 The {cass-short} Source Connector creates a consumer to receive new event messages from the CDC agent, but does not configure a dead letter topic. It is assumed that parallel instances, broker compute, and function worker compute will be sized to handle the workload.
 ====