rebasing main on mkdocs pt2

blog/articles/event-drive-app-knative-eventing-kogito.md

@@ -28,7 +28,7 @@ As part of the Serverless Workflow implementation, Kogito offers a Kubernetes Op
 
 To demonstrate how the Kogito workflow implementation works on Knative's event-driven architecture, we will use the [patient onboarding example](https://github.com/kiegroup/kogito-examples/tree/master/serverless-workflow-functions-events-quarkus). In this example, we simulate a workflow used in hospitals to onboard new patients and assign them to the correct doctor.
 
-The following image taken from the [specification examples page](https://github.com/serverlessworkflow/specification/blob/master/examples/examples.md#New-Patient-Onboarding) illustrates this workflow:
+The following image taken from the [specification examples page](https://github.com/serverlessworkflow/specification/tree/main/examples#New-Patient-Onboarding) illustrates this workflow:
 
 ![Patient onboarding workflow representation](/blog/articles/images/kogito-example-patientonboarding.png)
 *Patient Onboarding workflow representation*

docs/eventing/event-registry.md

@@ -62,7 +62,7 @@ kubectl get eventtype dev.knative.source.github.push-34cnb -o yaml
 Omitting irrelevant fields:
 
 ```yaml
-apiVersion: eventing.knative.dev/v1
+apiVersion: eventing.knative.dev/v1beta1
 kind: EventType
 metadata:
   name: dev.knative.source.github.push-34cnb

docs/eventing/samples/kafka/README.md

@@ -36,7 +36,7 @@ is to install it by using [Strimzi](https://strimzi.io).
    ```
 1. Describe the size of your Apache Kafka installation in `kafka.yaml`, like:
    ```yaml
-   apiVersion: kafka.strimzi.io/v1beta1
+   apiVersion: kafka.strimzi.io/v1beta2
    kind: Kafka
    metadata:
      name: my-cluster

docs/eventing/samples/kafka/channel/README.md

@@ -96,6 +96,8 @@ with `knative-messaging-kafka`. This indicates it is an Apache Kafka channel
 from Knative. It contains the name of the namespace, `default` in this example,
 followed by the actual name of the channel.
 
+**NOTE:** The topic of a Kafka channel is an implementation detail and records from it should not be consumed from different applications.
+
 ## Configuring the Knative broker for Apache Kafka channels
 
 To setup a broker that will use the new default Kafka channels, you must create
@@ -127,6 +129,8 @@ knative-messaging-kafka.default.default-kn2-trigger
 ...
 ```
 
+**NOTE:** The topic of a Kafka channel is an implementation detail and records from it should not be consumed from different applications.
+
 ## Creating a service and trigger to use the Apache Kafka broker
 
 To use the Apache Kafka based broker, let's take a look at a simple demo. Use

docs/eventing/samples/kafka/kafka.yaml

@@ -1,4 +1,4 @@
-apiVersion: kafka.strimzi.io/v1beta1
+apiVersion: kafka.strimzi.io/v1beta2
 kind: Kafka
 metadata:
   name: my-cluster

docs/eventing/sources/kafka-source/README.md

@@ -31,7 +31,7 @@ The `KafkaSource` reads all the messages, from all partitions, and sends those m
 - Replicas
 
   ```yaml
-  apiVersion: kafka.strimzi.io/v1beta1
+  apiVersion: kafka.strimzi.io/v1beta2
   kind: KafkaTopic
   metadata:
     name: knative-demo-topic

docs/eventing/sources/kafka-source/kafka-topic.yaml

@@ -12,7 +12,7 @@
 # See the License for the specific language governing permissions and
 # limitations under the License.
 
-apiVersion: kafka.strimzi.io/v1beta1
+apiVersion: kafka.strimzi.io/v1beta2
 kind: KafkaTopic
 metadata:
   name: knative-demo-topic

docs/getting-started/contributing/contributing.md

@@ -44,7 +44,8 @@ Once you have installed Material for MkDocs and all of the extensions, head over
 --8<-- "docs/snippets/links/main-docs-branch-link.md"
 and clone the repo.
 
-In your terminal, find your way over to the location of the cloned repo. Once you are in the main folder (.../docs) and run:
+In your terminal, find your way over to the location of the cloned repo. Once you are in the main folder and run:
+
 
 === "Local Preview"
     ```