articles (#170)

Author: aimurphy

modules/ROOT/pages/astream-faq.adoc

@@ -33,7 +33,7 @@ And finally {product} offers a user-friendly interface and free tier to satisfy
 
 == Why does {company} call {product} "serverless"?
 
-Running a {pulsar-reg} cluster that can handle at-scale workloads is not a trivial task.
+Running an {pulsar-reg} cluster that can handle at-scale workloads is not a trivial task.
 It requires many (virtual) machines to be configured in a very particular way.
 
 In traditional cloud environments, you would pay hourly for every machine whether they are being used for workloads or not, and you would carry the burden of maintaining the server infrastructure.

modules/apis/pages/api-operations.adoc

@@ -19,7 +19,7 @@ To send requests to the {product} {pulsar-short} Admin API, you need the followi
 
 * An active {astra} account with access to {product}.
 
-* A {product} tenant.
+* An {product} tenant.
 
 * A xref:operations:astream-token-gen.adoc[{pulsar-short} token] for your tenant.
 +

modules/developing/pages/gpt-schema-translator.adoc

@@ -3,7 +3,7 @@
 Systems in streaming pipelines can use different representations for schema and data types.
 
 Schema mapping is required to align congruent types in a pipeline.
-For example, to send data from a CDC-enabled {cass-reg} table to a {pulsar-reg} topic, you must define schema mapping between the {cass-short} table and the {pulsar-short} topic.
+For example, to send data from a CDC-enabled {cass-reg} table to an {pulsar-reg} topic, you must define schema mapping between the {cass-short} table and the {pulsar-short} topic.
 If the schema includes more complex data types, like maps and nested data structures, schema management becomes more difficult.
 
 Schema management is a complicated, tedious, and error-prone tasks that requires you to understand and translate multiple sets of schema rules.

modules/operations/pages/private-connectivity.adoc

@@ -65,7 +65,7 @@ The private link service pattern is the same across cloud providers, but the hos
 
 === Private connections for outbound traffic
 
-On a case-by-case basis, {product} can support private outbound traffic flowing from a {product} private endpoint to your private link service.
+On a case-by-case basis, {product} can support private outbound traffic flowing from an {product} private endpoint to your private link service.
 
 {company} opens a port on the tenant's firewall to allow connectors and functions running in a dedicated namespace on an {product} cluster to connect to your private network.
 Each tenant has its own firewall.