RHDEVDOCS-5458: Update sink -> target in dev console

_topic_maps/_topic_map.yml

@@ -4,7 +4,7 @@ Dir: about
 Distros: openshift-serverless
 Topics:
 - Name: Release notes
-  File: serverless-release-notes  
+  File: serverless-release-notes
 - Name: Serverless overview
   File: about-serverless
 - Name: Knative Serving overview
@@ -126,7 +126,7 @@ Topics:
   - Name: Resolving image tags to digests
     File: resolving-image-tags-to-digests
   - Name: Configuring TLS authentication
-    File: serverless-config-tls      
+    File: serverless-config-tls
   - Name: Restrictive network policies
     File: restrictive-network-policies
 - Name: Traffic splitting
@@ -221,15 +221,15 @@ Topics:
     File: serverless-kafka-developer-source
   - Name: Custom event sources
     File: serverless-custom-event-sources
-  - Name: Connecting an event source to a sink using the Developer perspective
-    File: serverless-sink-source-odc
+  - Name: Connecting an event source to a target by using the Developer perspective
+    File: serverless-target-source-odc
 - Name: Event sinks
   Dir: event-sinks
   Topics:
   - Name: Event sinks overview
     File: serverless-event-sinks
   - Name: Creating event sinks
-    File: serverless-creating-sinks    
+    File: serverless-creating-sinks
   - Name: Sink for Apache Kafka
     File: serverless-kafka-developer-sink
 - Name: Brokers

eventing/event-sources/serverless-target-source-odc.adoc

@@ -0,0 +1,10 @@
+:_content-type: ASSEMBLY
+include::_attributes/common-attributes.adoc[]
+[id="serverless-target-source-odc"]
+= Connecting an event source to a target by using the Developer perspective
+:context: serverless-target-source-odc
+
+When you create an event source by using the {ocp-product-title} web console, you can specify a target that events are sent to from that source. The target can be any addressable or callable resource that can receive incoming events from other resources.
+
+// Connect targets to sources in ODC
+include::modules/serverless-connect-target-source-odc.adoc[leveloffset=+1]

modules/odc-creating-apiserversource.adoc

@@ -6,7 +6,7 @@
 [id="odc-creating-apiserversource_{context}"]
 = Creating an API server source by using the web console
 
-After Knative Eventing is installed on your cluster, you can create an API server source by using the web console. Using the {ocp-product-title} web console provides a streamlined and intuitive user interface to create an event source. 
+After Knative Eventing is installed on your cluster, you can create an API server source by using the web console. Using the {ocp-product-title} web console provides a streamlined and intuitive user interface to create an event source.
 
 .Prerequisites
 
@@ -32,7 +32,7 @@ You can switch between the *Form view* and *YAML view*. The data is persisted wh
 // .. Select *Resource* as the *Mode*. *Mode* is the mode that the receive adapter controller runs in. `Ref` sends only the reference to the resource. `Resource` sends the full resource.
 // TODO: clarify what this is used for. Out of scope for this PR since not required.
 .. Select the *Service Account Name* for the service account that you created.
-.. Select the *Sink* for the event source. A *Sink* can be either a *Resource*, such as a channel, broker, or service, or a *URI*.
+.. Select the *Target* for the event source. This can be either a *Resource*, such as a channel, broker, or service, or a *URI*.
 . Click *Create*.
 
 .Verification

modules/serverless-connect-func-source-odc.adoc

@@ -19,7 +19,7 @@ Functions are deployed as Knative services on an {ocp-product-title} cluster. Wh
 
 . Create an event source of any type, by navigating to *+Add* -> *Event Source* and selecting the event source type that you want to create.
 
-. In the *Sink* section of the *Create Event Source* form view, select your function in the *Resource* list.
+. In the *Target* section of the *Create Event Source* form view, select your function in the *Resource* list.
 
 . Click *Create*.
 

modules/serverless-connect-sink-source-odc.adoc → modules/serverless-connect-target-source-odc.adoc

@@ -1,10 +1,10 @@
 // Module included in the following assemblies:
 //
-// * serverless/eventing/event-sources/serverless-sink-source-odc.adoc
+// * serverless/eventing/event-sources/serverless-target-source-odc.adoc
 
 :_content-type: PROCEDURE
-[id="serverless-connect-sink-source-odc_{context}"]
-= Connect an event source to a sink using the Developer perspective
+[id="serverless-connect-target-source-odc_{context}"]
+= Connect an event source to a target by using the Developer perspective
 
 .Prerequisites
 
@@ -17,7 +17,7 @@
 
 . Create an event source of any type, by navigating to *+Add* -> *Event Source* and selecting the event source type that you want to create.
 
-. In the *Sink* section of the *Create Event Source* form view, select your sink in the *Resource* list.
+. In the *Target* section of the *Create Event Source* form view, select your sink in the *Resource* list.
 
 . Click *Create*.
 

modules/serverless-kafka-source-odc.adoc

@@ -24,7 +24,7 @@ After the Knative broker implementation for Apache Kafka is installed on your cl
 .. Add a comma-separated list of *Topics*.
 .. Add a *Consumer Group*.
 .. Select the *Service Account Name* for the service account that you created.
-.. Select the *Sink* for the event source. A *Sink* can be either a *Resource*, such as a channel, broker, or service, or a *URI*.
+.. Select the *Target* for the event source. This can be either a *Resource*, such as a channel, broker, or service, or a *URI*.
 .. Enter a *Name* for the Kafka event source.
 . Click *Create*.
 

modules/serverless-odc-create-containersource.adoc

@@ -32,7 +32,7 @@ You can switch between the *Form view* and *YAML view*. The data is persisted wh
 // Optional? Add options and what they mean.
 // Same for env variables...
 .. Optional: In the *Environment variables* field, add any environment variables to set in the container.
-.. In the *Sink* section, add a sink where events from the container source are routed to. If you are using the *Form* view, you can choose from the following options:
+.. In the *Target* section, add a sink where events from the container source are routed to. If you are using the *Form* view, you can choose from the following options:
 ... Select *Resource* to use a channel, broker, or service as a sink for the event source.
 ... Select *URI* to specify where the events from the container source are routed to.
 

modules/serverless-pingsource-odc.adoc

@@ -48,7 +48,7 @@ You can configure the *PingSource* settings by using the *Form view* or *YAML vi
 ====
 .. Enter a value for *Schedule*. In this example, the value is `*/2 * * * *`, which creates a PingSource that sends a message every two minutes.
 .. Optional: You can enter a value for *Data*, which is the message payload.
-.. Select a *Sink*. This can be either a *Resource* or a *URI*. In this example, the `event-display` service created in the previous step is used as the *Resource* sink.
+.. Select a *Target*. This can be either a *Resource* or a *URI*. In this example, the `event-display` service created in the previous step is used as the *Resource* sink.
 .. Click *Create*.
 
 .Verification

modules/serverless-sinkbinding-odc.adoc

@@ -96,7 +96,7 @@ You can configure the *Sink Binding* settings by using the *Form view* or *YAML
 ====
 The `CronJob` kind is not supported directly by {ServerlessProductName} sink binding, so the *Kind* field must target the `Job` objects created by the cron job, rather than the cron job object itself.
 ====
-.. Select a *Sink*. This can be either a *Resource* or a *URI*. In this example, the `event-display` service created in the previous step is used as the *Resource* sink.
+.. Select a *Target*. This can be either a *Resource* or a *URI*. In this example, the `event-display` service created in the previous step is used as the *Resource* sink.
 .. In the *Match labels* section:
 ... Enter `app` in the *Name* field.
 ... Enter `heartbeat-cron` in the *Value* field.