docs: JX-328: Trims the long descriptions to avoid truncation (#630)

Author: bredamc

docs/connectors/getting-started-connectors/README.adoc

@@ -107,7 +107,7 @@ endif::[]
 ifdef::qs[]
 [#description]
 ====
-Learn how to configure connections between {product-long-kafka} and third-party systems by using {product-long-connectors}.
+Configure connections between an {product-kafka} instance and third-party systems.
 ====
 
 [#introduction]
@@ -116,7 +116,7 @@ Welcome to the quick start for {product-long-connectors}.
 
 In this quick start, you learn how to create a source connector and sink connector and send data to and from {product-kafka}.
 
-A _source_ connector allows you to send data from an external system to {product-kafka}. 
+A _source_ connector allows you to send data from an external system to {product-kafka}.
 
 A _sink_ connector allows you to send data from {product-kafka} to an external system.
 ====
@@ -128,7 +128,7 @@ endif::[]
 
 [role="_abstract"]
 
-Before you use {product-connectors}, you must complete the following prerequisites: 
+Before you use {product-connectors}, you must complete the following prerequisites:
 
 * Determine which {openshift} environment to use for your _{connectors} namespace_. The {connectors} namespace is where your {product-connectors} instances are deployed.
 
@@ -252,7 +252,7 @@ Click *Next*.
 
 . Select one of the following error handling policies for your {connectors} instance:
 +
-* *Stop*: If a message fails to send, the {connectors} instance stops running and changes its status to the *Failed* state. You can view the error message. 
+* *Stop*: If a message fails to send, the {connectors} instance stops running and changes its status to the *Failed* state. You can view the error message.
 * *Ignore*: If a message fails to send, the {connectors} instance ignores the error and continues to run. No error message is logged.
 * *Dead letter queue*: If a message fails to send, the {connectors} instance sends error details to the Kafka topic that you created for the DLQ.
 +

docs/kafka/nodejs-kafka/README.adoc

@@ -116,7 +116,7 @@ NOTE: The example Node.js application in this quick start uses the https://kafka
 ifdef::qs[]
 [#description]
 ====
-Learn how to manually connect a Node.js application to a Kafka instance in {product-long-kafka} and then produce and consume messages.
+Manually connect a Node.js application to a Kafka instance and then produce and consume messages.
 ====
 
 [#introduction]

docs/kafka/quarkus-kafka/README.adoc

@@ -115,7 +115,7 @@ endif::[]
 ifdef::qs[]
 [#description]
 ====
-Learn how to manually connect a Quarkus application to a Kafka instance in {product-long-kafka} and then produce and consume messages.
+Manually connect a Quarkus application to a Kafka instance and then produce and consume messages.
 ====
 
 [#introduction]

docs/registry/quarkus-registry/README.adoc

@@ -118,7 +118,7 @@ endif::[]
 ifdef::qs[]
 [#description]
 ====
-Learn how to manually connect a Quarkus application to a Kafka instance in {product-long-kafka} and a {registry} instance in {product-long-registry}. The application will use the Kafka instance to produce and consume messages and a schema stored in the {registry} instance to serialize/deserialize the messages.
+Manually connect a Quarkus application to a Kafka instance and to a {registry} instance.
 ====
 
 [#introduction]
@@ -161,7 +161,7 @@ This Quarkus example application includes producer and consumer processes that s
 
 .Prerequisites
 * You have a service account with write access to Kafka and {registry} instances and have stored your credentials securely (see {base-url}{getting-started-url-kafka}[Getting started with {product-long-kafka}^] and {base-url}{getting-started-url-registry}[Getting started with {product-long-registry}^]).
-* You have the bootstrap server endpoint for the Kafka instance. To get this information, select your Kafka instance in the {service-url-kafka}[{product-kafka} web console^], select the options icon (three vertical dots), and click *Connection*. 
+* You have the bootstrap server endpoint for the Kafka instance. To get this information, select your Kafka instance in the {service-url-kafka}[{product-kafka} web console^], select the options icon (three vertical dots), and click *Connection*.
 * You have the Core Registry API endpoint for the {registry} instance. To get this information, select your {registry} instance in the {service-url-registry}[{product-registry} web console^], select the options icon (three vertical dots) and click *Connection*. Copy the *Core Registry API* endpoint supported by the Apicurio serializer/deserializer (SerDes) used in this example.
 * You have the SASL/OAUTHBEARER token endpoint used by the {registry} and Kafka instances. To get this information, select your {registry} instance in the {service-url-registry}[{product-registry} web console^], select the options icon (three vertical dots) and click *Connection*. Copy the *Token endpoint URL* value.