docs: minor clean up from downstream testing (#3105)

* docs: minor clean up from downstream testing

* docs: clean up contrib doc, fix a few typos

Author: smccarthy-ie

CONTRIBUTING.md

@@ -77,24 +77,24 @@ Be sure to test your pull request using all storage variants:
 
 ### Customizing Registry supported ArtifactTypes
 
-Apicurio Registry is a modular project and it allows re-use of the produced artifacts in order to extend and enanche the functionalities.
+Apicurio Registry is a modular project and allows reuse of artifact types to extend and enhance functionality.
 
-More specifically it's possible to modify the currently supported artifact types and add new onces by providing an higher priority  `io.apicurio.registry.types.bigquery.provider.ArtifactTypeUtilProviderImpl` to the DI framework.
+You can modify the currently supported artifact types and add new types by providing a higher priority implementation of `io.apicurio.registry.types.<my-type>.provider.ArtifactTypeUtilProviderImpl` to the dependency injection framework.
 
-In [this repository](https://github.com/andreaTP/apicurio-registry-with-bigquery-example) you can find an example where we add a demo BigQuery support.
+In [this GitHub repository](https://github.com/andreaTP/apicurio-registry-with-bigquery-example), you can find an example where we add demo `BigQuery` support.
 
-Those are the interesting parts:
+The important parts are as follows:
 
- - use Apicurio Registry [as a dependency](https://github.com/andreaTP/apicurio-registry-with-bigquery-example/blob/66c5d18d9c0b5e246597b79e5c5b82a54752a65d/pom.xml#L45-L49)
- - provide [an higher priority `ArtifactTypeUtilProviderImpl`](https://github.com/andreaTP/apicurio-registry-with-bigquery-example/blob/66c5d18d9c0b5e246597b79e5c5b82a54752a65d/src/main/java/io/apicurio/registry/types/bigquery/provider/ArtifactTypeUtilProviderImpl.java#L30-L33)
- - tweak [the provider list](https://github.com/andreaTP/apicurio-registry-with-bigquery-example/blob/66c5d18d9c0b5e246597b79e5c5b82a54752a65d/src/main/java/io/apicurio/registry/types/bigquery/provider/ArtifactTypeUtilProviderImpl.java#L48) in the constructor to include the additional artifact type
+ - Use [Apicurio Registry as a dependency](https://github.com/andreaTP/apicurio-registry-with-bigquery-example/blob/66c5d18d9c0b5e246597b79e5c5b82a54752a65d/pom.xml#L45-L49)
+ - Provide a [higher priority `ArtifactTypeUtilProviderImpl`](https://github.com/andreaTP/apicurio-registry-with-bigquery-example/blob/66c5d18d9c0b5e246597b79e5c5b82a54752a65d/src/main/java/io/apicurio/registry/types/bigquery/provider/ArtifactTypeUtilProviderImpl.java#L30-L33)
+ - [Update the provider list](https://github.com/andreaTP/apicurio-registry-with-bigquery-example/blob/66c5d18d9c0b5e246597b79e5c5b82a54752a65d/src/main/java/io/apicurio/registry/types/bigquery/provider/ArtifactTypeUtilProviderImpl.java#L48) in the constructor to include the additional artifact type
 
 **NOTES:**
 
-- when creating an artifact of a type not included in the default you ALWAYS need to specify the appropriate artifact type
-- the UI will show the plain name of the additional type and won't have an appropriate icon to identify it
+- When creating an artifact of a type that is not included in the default, you must _always_ specify the appropriate artifact type.
+- The registry UI will show the plain name of the additional type and won't have an appropriate icon to identify it.
 
 ## The small print
 
-This project is an open source project, please act responsibly, be nice, polite and enjoy!
+This project is an open source project. Please act responsibly, be nice, polite and enjoy!
 

docs/modules/ROOT/partials/getting-started/con-registry-serde.adoc

@@ -32,9 +32,4 @@ These implementations include custom Java classes for each supported message typ
 
 [role="_additional-resources"]
 .Additional resources
-ifdef::apicurio-registry,rh-service-registry[]
 * {kafka-client-serdes}
-endif::[]
-ifdef::rh-openshift-sr[]
-* link:https://access.redhat.com/documentation/en-us/red_hat_integration/2021.q3/html/service_registry_user_guide/using-kafka-client-serdes[Red Hat Integration Service Registry documentation on Kafka client SerDes]
-endif::[]

docs/modules/ROOT/partials/getting-started/con-registry-storage.adoc

@@ -7,7 +7,7 @@
 {registry} provides the following options for the underlying storage of registry data: 
 
 .{registry} data storage options 
-[%header,cols="2,4"] 
+[%header,cols="1,3"] 
 |===
 |Storage option
 |Description
@@ -17,14 +17,14 @@ ifdef::apicurio-registry[]
 |The in-memory storage option is suitable for a development environment only. All data is lost when restarting {registry} with this storage. The PostgreSQL or Kafka storage option is recommended for a production environment.
 endif::[]
 
-|PostgreSQL {registry-db-version} database  
+|PostgreSQL database  
 |PostgreSQL is the recommended data storage option for performance, stability, and data management (backup/restore, and so on) in a production environment.
 
 ifdef::apicurio-registry[]
-|Apache Kafka {registry-kafka-version}
+|Apache Kafka 
 endif::[]
 ifdef::rh-service-registry[]
-|{kafka-streams} {registry-streams-version} 
+|{kafka-streams} 
 endif::[]
 |Kafka storage is provided for production environments where database management expertise is not available, or where storage in Kafka is a specific requirement.
 |===

docs/modules/ROOT/partials/getting-started/proc-installing-postgresql-operatorhub.adoc

@@ -22,7 +22,7 @@ If you do not already have a PostgreSQL database Operator installed, you can ins
 
 . In the left navigation menu, click *Operators* and then *OperatorHub*.
 
-. In the *Filter by keyword* text box, enter `PostgreSQL` to find an Operator suitable for your environment, for example, *Crunchy PostgreSQL for OpenShift* or *PostgreSQL Operator by Dev4Ddevs.com*.
+. In the *Filter by keyword* text box, enter `PostgreSQL` to find an Operator suitable for your environment, for example, *Crunchy PostgreSQL for OpenShift*.
 
 . Read the information about the Operator, and click *Install* to display the Operator subscription page.
 

docs/modules/ROOT/partials/getting-started/proc-registry-serdes-config-consumer.adoc

@@ -16,7 +16,7 @@ This procedure describes how to configure a Kafka consumer client written in Jav
 
 . Configure the client with the URL of {registry}. For example:
 +
-[source,shell,subs="+quotes,attributes"]
+[source,java,subs="+quotes,attributes"]
 ----
 String registryUrl = "https://registry.example.com/apis/registry/v2";
 Properties props = new Properties();

docs/modules/ROOT/partials/getting-started/proc-registry-serdes-config-stream.adoc

@@ -16,7 +16,7 @@ This procedure describes how to configure a Kafka Streams client written in Java
 
 . Create and configure a Java client with the {registry} URL:
 +
-[source,shell,subs="+quotes,attributes"]
+[source,java,subs="+quotes,attributes"]
 ----
 String registryUrl = "https://registry.example.com/apis/registry/v2";
 

docs/modules/ROOT/partials/getting-started/proc-setting-up-postgresql-storage.adoc

@@ -56,7 +56,7 @@ ifdef::apicurio-registry[]
 . Click *Installed Operators* > *{registry}* > *ApicurioRegistry* > *Create ApicurioRegistry*.
 endif::[]
 ifdef::rh-service-registry[]
-. Click *Installed Operators* > *Red Hat Integration - {registry}* > *ApicurioRegistry* > *Create ApicurioRegistry*.
+. Click *Installed Operators* > *Red Hat Integration - Service Registry* > *ApicurioRegistry* > *Create ApicurioRegistry*.
 endif::[]
 
 . Paste in the following custom resource definition, and edit the values for the database `url` and credentials to match your environment:

docs/modules/ROOT/partials/getting-started/proc-writing-registry-client.adoc

@@ -52,10 +52,4 @@ When the client is created, you can use all the operations available in the {reg
 .Additional resources
 * For an open source example of how to use and customize the {registry} client, see the https://github.com/Apicurio/apicurio-registry-examples[Registry REST client demonstration example]
 
-* For details on how to use the {registry} Kafka client serializers/deserializers (SerDes) in producer and consumer applications, see 
-ifdef::apicurio-registry,rh-service-registry[]
-{kafka-client-serdes}
-endif::[]
-ifdef::rh-openshift-sr[]
-link:https://access.redhat.com/documentation/en-us/red_hat_integration/2021.q3/html/service_registry_user_guide/using-kafka-client-serdes[Red Hat Integration Service Registry Kafka client SerDes]
-endif::[]
+* For details on how to use the {registry} Kafka client serializers/deserializers (SerDes) in producer and consumer applications, see {kafka-client-serdes}.

docs/modules/ROOT/partials/getting-started/ref-registry-client.adoc

@@ -48,9 +48,4 @@ You can configure Transport Layer Security (TLS) authentication for the {registr
 [role="_additional-resources"]
 .Additional resources
 * For details on how to configure authentication for {registry} Kafka client serializers/deserializers (SerDes), see 
-ifdef::apicurio-registry,rh-service-registry[]
-{kafka-client-serdes}
-endif::[]
-ifdef::rh-openshift-sr[]
-link:https://access.redhat.com/documentation/en-us/red_hat_integration/2021.q3/html/service_registry_user_guide/configuring-kafka-client-serdes[Red Hat Integration Service Registry Kafka client SerDes configuration].
-endif::[]
+{kafka-client-serdes}.

docs/modules/ROOT/partials/shared/attributes-links.adoc

@@ -152,8 +152,8 @@
 :RegistryProductURL: service_registry 
 
 ifdef::RHAF[]
-:productpkg: apicurio_registry
-:RegistryProductURL: red_hat_build_of_apicurio_registry
+:productpkg: red_hat_build_of_apicurio_registry 
+:RegistryProductURL: apicurio_registry
 :ServiceRegistryURLVersion: 2.3
 endif::[]
 

docs/modules/ROOT/partials/shared/attributes.adoc

@@ -21,7 +21,7 @@ ifndef::service-registry-downstream[]
 :apicurio-registry:
 :registry: Apicurio Registry
 :registry-name-full: Apicurio Registry
-:registry-version: 2.3
+:registry-version: 2.4
 :registry-docker-version: latest-release 
 :registry-v1: 1.3.x
 :operator-version: 1.0.0