diff --git a/modules/ROOT/pages/astream-subscriptions-exclusive.adoc b/modules/ROOT/pages/astream-subscriptions-exclusive.adoc index 896b6f9..b4280e3 100644 --- a/modules/ROOT/pages/astream-subscriptions-exclusive.adoc +++ b/modules/ROOT/pages/astream-subscriptions-exclusive.adoc @@ -67,7 +67,7 @@ In the `SimplePulsarConsumer` terminal, the consumer begins consuming the produc . In a new terminal window, try to run another instance of `SimplePulsarConsumer.java`. + -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: + .Result [source,console] diff --git a/modules/ROOT/pages/astream-subscriptions-keyshared.adoc b/modules/ROOT/pages/astream-subscriptions-keyshared.adoc index 064c883..3f92bb6 100644 --- a/modules/ROOT/pages/astream-subscriptions-keyshared.adoc +++ b/modules/ROOT/pages/astream-subscriptions-keyshared.adoc @@ -124,7 +124,7 @@ In the `SimplePulsarConsumer` terminal, the consumer begins receiving messages: . In a new terminal window, try to run a new instance of `SimplePulsarConsumer.java`. + -The new consumer can't subscribe to the topic because the `SimplePulsarConsumer` configuration reserved the entire hash range for the first consumer: +The new consumer cannot subscribe to the topic because the `SimplePulsarConsumer` configuration reserved the entire hash range for the first consumer: + .Result [source,console] diff --git a/modules/ROOT/pages/astream-subscriptions-shared.adoc b/modules/ROOT/pages/astream-subscriptions-shared.adoc index 811ea84..dd007ad 100644 --- a/modules/ROOT/pages/astream-subscriptions-shared.adoc +++ b/modules/ROOT/pages/astream-subscriptions-shared.adoc @@ -78,7 +78,7 @@ The new consumer subscribes to the topic and consumes messages: ---- Because this test uses shared subscriptions, you can attach multiple consumers to the topic. -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. To continue testing the shared subscription configuration, you can continue running new instances of `SimplePulsarConsumer.java` in new terminal windows. All the consumers subscribe to the topic and consume messages in a round-robin fashion. diff --git a/modules/developing/pages/astream-kafka.adoc b/modules/developing/pages/astream-kafka.adoc index ada9dde..9c24b9d 100644 --- a/modules/developing/pages/astream-kafka.adoc +++ b/modules/developing/pages/astream-kafka.adoc @@ -21,7 +21,7 @@ This document will help you get started producing and consuming Kafka messages o + [IMPORTANT] ==== -You can't remove the Kafka namespaces created on your tenant with this step. +You cannot remove the Kafka namespaces created on your tenant with this step. You must remove the tenant itself to remove these namespaces. ==== diff --git a/modules/developing/pages/astream-rabbit.adoc b/modules/developing/pages/astream-rabbit.adoc index 01092d4..177d1e7 100644 --- a/modules/developing/pages/astream-rabbit.adoc +++ b/modules/developing/pages/astream-rabbit.adoc @@ -21,7 +21,7 @@ Get started producing and consuming RabbitMQ messages on a {pulsar-short} cluste + [IMPORTANT] ==== -You can't remove the RabbitMQ namespace created on your tenant with this step. +You cannot remove the RabbitMQ namespace created on your tenant with this step. You must remove the tenant itself to remove this namespace. ==== diff --git a/modules/operations/pages/astream-limits.adoc b/modules/operations/pages/astream-limits.adoc index bbfb0fc..81b9e9a 100644 --- a/modules/operations/pages/astream-limits.adoc +++ b/modules/operations/pages/astream-limits.adoc @@ -9,7 +9,7 @@ In general, xref:operations:astream-pricing.adoc#dedicated-clusters[Streaming Ca == {product} guardrails Guardrails are provisioned in the default settings for {product}. -You can't directly change these guardrails. +You cannot directly change these guardrails. For Streaming Capacity Units, some guardrails can be changed by contacting {support_url}[{company} Support]. [cols="1,1,1"] @@ -21,7 +21,7 @@ a| * Shared clusters: 10 * Streaming Capacity Units: Unlimited -|This limit can't be changed for shared clusters. +|This limit cannot be changed for shared clusters. |Number of namespaces per tenant |All clusters: 20 @@ -306,7 +306,7 @@ Each function instance is assigned a specific amount of CPU and memory which can Each {pulsar-short} function running on {product} has a minimum of one function instance allocated to it. Functions and connector resources for function instances are set in the control plane based as resource limits. -You can't customize these resources. +You cannot customize these resources. The default settings are as follows: @@ -328,7 +328,7 @@ The default settings are as follows: == Immutable configurations -The following configurations can't be changed: +The following configurations cannot be changed: * Data persistency (`En`, `Qw`, `Qa`) * `Managedledger` policy/deletion diff --git a/modules/operations/pages/monitoring/new-relic.adoc b/modules/operations/pages/monitoring/new-relic.adoc index 1029496..4830622 100644 --- a/modules/operations/pages/monitoring/new-relic.adoc +++ b/modules/operations/pages/monitoring/new-relic.adoc @@ -12,7 +12,7 @@ While there are multiple ways to https://docs.newrelic.com/docs/infrastructure/p xref:monitoring/integration.adoc[Install an extra Prometheus server] to act as a bridge to forward scraped {product} metrics to New Relic. -This is required because {product} is a managed service, and you can't modify the {product} Prometheus server as required by the New Relic Prometheus write integration. +This is required because {product} is a managed service, and you cannot modify the {product} Prometheus server as required by the New Relic Prometheus write integration. == Configure New Relic