Merge pull request kabanero-io#336 from kabanero-io/335-jantley-reviewedits

review edits and more terminology

Author: tseelbach

ref/general/configuration/kabanero-cr-config.adoc

@@ -10,7 +10,7 @@ installation.  This description includes the locations of the application
 stacks, and how the Kabanero CLI should interact with GitHub.
 
 The `Spec` section of the `Kabanero` instance describes the desired
-configuration.  The `Status` section is populated by the Kabanero operator,
+configuration.  The `Status` section is populated by the product operator,
 and shows the versions of the components that make up Kabanero.  In some
 cases, the `Status` also contains URLs that can be used to interact with
 the components of Kabanero.
@@ -87,7 +87,7 @@ specify the following fields:
     three hours, thirty minutes and thirty seconds.
 ** `landing`
 *** `enable` - Controls whether the Kabanero landing page is deployed by
-    the Kabanero operator.  Valid values are `true` and `false`.  The default
+    the product operator.  Valid values are `true` and `false`.  The default
     value is `true`.
 ** `codeReadyWorkspaces`
 *** `enable` - Controls whether Kabanero will deploy an instance of 
@@ -120,7 +120,7 @@ specify the following fields:
     define the realm that the SSO server will use.  For more information
     about setting up the secret, see link:rhsso.html[the SSO configuration instructions].
 
-The following `Status` fields are maintained by the Kabanero operator to
+The following `Status` fields are maintained by the product operator to
 provide information about the installed components, and the health of the
 Kabanero instance:
 
@@ -182,7 +182,7 @@ Kabanero instance:
 *** `message` - Provides more details for a `ready` status of `False`.
 *** `version` - The version of the landing page that was deployed.
 ** `appsody` - Contains information about the application operator that was
-   deployed by the Kabanero operator.
+   deployed by the product operator.
 *** `ready` - The overall status of the application operator.  A value
     of `True` indicates the operator was deployed successfully.  A value of
     `False` indicates there was a problem, and more information can be found
@@ -203,7 +203,7 @@ Kabanero instance:
     kAppNav.  This information is copied from the `Route` for the kAppNav API
     service.
 ** `codereadyWorkspaces` - Contains information about the CodeReady
-   Workspaces instance that is deployed by the Kabanero operator.
+   Workspaces instance that is deployed by the product operator.
 *** `ready` - The overall status of CodeReady Workspaces.  A value of `True`
     indicates it was installed and configured successfully.  A value of
     `False` indicates that there was a problem, and more information can be

ref/general/configuration/rhsso.adoc

@@ -5,7 +5,7 @@
 :sectanchors:
 = Configuring Kabanero with Red Hat Single Sign On
 
-After Kabanero is installed, the Kabanero operator can optionally create an instance of Red Hat Single Sign On (RHSSO) for development use.
+After Kabanero is installed, the product operator can optionally create an instance of Red Hat Single Sign On (RHSSO) for development use.
 To create the RHSSO instance, create the required secret and the persistent volume and then edit the Kabanero custom resource (CR).
 
 . Create a persistent volume (PV) of size 1 GB. The type of storage used might vary depending on the environment where OpenShift is installed.

ref/general/configuration/stack-cr-config.adoc

@@ -27,7 +27,7 @@ specify the following fields:
     that this version of this stack should remain in.  An empty
     value results in this version being activated.  Other valid
     values are `active` and `inactive`.  If either of these values
-    is provided, the Kabanero operator will not attempt to change
+    is provided, the product operator will not attempt to change
     the state for this version, even if the stack is removed from
     the stack index which caused this Stack CR to be created.
     This behavior can be used to permanently activate or deactivate

ref/general/configuration/stack-install.adoc

@@ -56,7 +56,7 @@ For more information about other fields that can be customized in the Kabanero C
 +
 After editing, save your changes.  The updated Kabanero CR instance is applied to your cluster.
 
-. The Kabanero operator will now load the stacks in the repository.  To see a list of all stacks in the `kabanero` namespace, use `oc get stacks -n kabanero`.  If the kabanero-operator is unable to apply the stacks, the `Status` section of the Kabanero CR instance or the Stack CR instances will contain more information.
+. The product operator will now load the stacks in the repository.  To see a list of all stacks in the `kabanero` namespace, use `oc get stacks -n kabanero`.  If the kabanero-operator is unable to apply the stacks, the `Status` section of the Kabanero CR instance or the Stack CR instances will contain more information.
 
 == Need help?
 If you have questions, we would like to hear from you.

ref/general/configuration/tekton-webhooks.adoc

@@ -1,17 +1,17 @@
 :page-layout: doc
 :page-doc-category: Configuration
-:page-title: Connecting Kabanero to GitHub with webhooks
+:page-title: Connecting to GitHub with webhooks
 :sectanchors:
 :page-doc-number: 5.0
-= Connecting Kabanero to GitHub with webhooks
+= Connecting to GitHub with webhooks
 
 A webhook is an outbound HTTP request that helps you create a relationship between your GitHub repository and a particular URL, in this case a https://github.com/kabanero-io/kabanero-pipelines/blob/master/README.md[pipeline, window="_blank"]. After you configure the webhook, changes you make in your GitHub repository will trigger the pipeline and its associated tasks.
 
 == Prerequisites
 
 * A GitHub repository
-* https://github.com/kabanero-io/kabanero-foundation/tree/master/scripts[Kabanero Foundation, window="_blank"].
-** Your Kabanero installation must include an instance of the https://github.com/tektoncd/dashboard#installing-the-latest-release[pipelines dashboard, window="_blank"] with the https://github.com/tektoncd/experimental/blob/master/webhooks-extension/README.md[webhooks extension, window="_blank"] and https://github.com/tektoncd/triggers/tree/v0.1.0/docs#tekton-triggers[triggers, window="_blank"] installed.
+* https://kabanero.io/docs/ref/general/installation/installing-kabanero-foundation.md[Kabanero Foundation, window="_blank"].
+** The product operator installation will include an instance of the pipelines dashboard with the webhooks extension and triggers.
 
 == Create a persistent volume
 Pipelines need a persistent volume. For more information, see *Setting up a persistent volume to run pipelines* in the https://kabanero.io/guides/working-with-pipelines/[Build and deploy applications with pipelines, window="_blank"] guide.
@@ -54,14 +54,14 @@ Namespace::
 Select the Kubernetes namespace in which you want to run your pipeline. In this case, choose `kabanero`.
 
 Pipeline::
-Select the pipeline in your target Namespace. PipelineRuns (and their accompanying PipelineResources) are created in this namespace. For more information, see https://github.com/kabanero-io/kabanero-pipelines#kabanero-pipelines[Kabanero Pipelines, window="_blank"].
+Select the pipeline in your target Namespace. PipelineRuns (and their accompanying PipelineResources) are created in this namespace. For more information, see https://github.com/kabanero-io/kabanero-pipelines#kabanero-pipelines[Pipelines, window="_blank"].
 
 Service Account::
 Select a service account to be used by the PipelineRun. There are two default service account options. Either of these accounts can be used as a template to create your own customized service accounts that fit your pipeline requirements.
 
 * If you are deploying pipelines in a single namespace, the `pipeline` service account is provided, which has permissions to build and push an image. This service account can be used with simple pipelines. However, it has limited access to the current namespace and does not work for cross-namespace operations and deployments.
 
-* If you need to deploy pipelines across multiple namespaces, the product operator provides the `kabanero-pipeline` service account with this capability. If you are running a custom pipeline that requires more or less access than the kabanero-pipeline service account is configured to provide, do not edit this account. Instead, create a new service account, such as `custom-kabanero-pipeline-sa`, and configure it according to your needs. For example service accounts, see the link:https://github.com/kabanero-io/kabanero-pipelines/tree/master/pipelines/common[Kabanero pipelines repo].
+* If you need to deploy pipelines across multiple namespaces, the product operator provides the `kabanero-pipeline` service account with this capability. If you are running a custom pipeline that requires more or less access than the kabanero-pipeline service account is configured to provide, do not edit this account. Instead, create a new service account, such as `custom-kabanero-pipeline-sa`, and configure it according to your needs using one of the provided service accounts as an example.
 
 Docker registry::
 Select the Docker registry where any built images are pushed. Use the same Docker registry that you created a secret for previously. For Docker Hub, use `index.docker.io/<docker_id>`. For an internal registry, use `docker-registry.default.svc:5000/kabanero`. If the namespace that is associated with your internal registry is not `kabanero`, use  `docker-registry.default.svc:5000/your-namespace`.
@@ -79,7 +79,7 @@ Select the Docker registry where any built images are pushed. Use the same Docke
 . Check the PipelineRun from your pipelines dashboard.
 * From your pipelines dashboard, select `PipelineRuns` from the sidebar menu. Look for the PipelineRun you just kicked off.
 
-Your GitHub repo is connected to Kabanero with a webhook. Changes in your code can now automatically trigger tasks that are specified by the pipeline.
+Your GitHub repo is connected using a webhook. Changes in your code can now automatically trigger tasks that are specified by the pipeline. If you don't see a PipelineRun in your dashboard, see the https://kabanero.io/docs/ref/general/reference/troubleshooting.html#errors-when-using-a-webhook-to-trigger-pipelines[troubleshooting guide].
 
 == Deleting a webhook