Merge pull request #44125 from Amrita42/BZ2033580new

BZ2033580: corrected wrong instances of plug-in and parameter

Author: kalexand-rh

logging/cluster-logging-release-notes.adoc

@@ -113,15 +113,15 @@ To see these metrics, open the *Administrator* perspective in the {product-title
 
 * Before this update, the `kibana-proxy` Pod sometimes entered the `CrashLoopBackoff` state and logged the following message `Invalid configuration: cookie_secret must be 16, 24, or 32 bytes to create an AES cipher when pass_access_token == true or cookie_refresh != 0, but is 29 bytes.` The exact actual number of bytes could vary. With this update, the generation of the Kibana session secret has been corrected, and the kibana-proxy Pod no longer enters a `CrashLoopBackoff` state due to this error. (link:https://issues.redhat.com/browse/LOG-1446[LOG-1446])
 
-* Before this update, the AWS CloudWatch Fluentd plugin logged its AWS API calls to the Fluentd log at all log levels, consuming additional {product-title} node resources. With this update, the AWS CloudWatch Fluentd plugin logs AWS API calls only at the "debug" and "trace" log levels. This way, at the default "warn" log level, Fluentd does not consume extra node resources. (link:https://issues.redhat.com/browse/LOG-1071[LOG-1071])
+* Before this update, the AWS CloudWatch Fluentd plug-in logged its AWS API calls to the Fluentd log at all log levels, consuming additional {product-title} node resources. With this update, the AWS CloudWatch Fluentd plug-in logs AWS API calls only at the "debug" and "trace" log levels. This way, at the default "warn" log level, Fluentd does not consume extra node resources. (link:https://issues.redhat.com/browse/LOG-1071[LOG-1071])
 
-* Before this update, the Elasticsearch OpenDistro security plugin caused user index migrations to fail. This update resolves the issue by providing a newer version of the plugin. Now, index migrations proceed without errors. (link:https://issues.redhat.com/browse/LOG-1276[LOG-1276])
+* Before this update, the Elasticsearch OpenDistro security plug-in caused user index migrations to fail. This update resolves the issue by providing a newer version of the plug-in. Now, index migrations proceed without errors. (link:https://issues.redhat.com/browse/LOG-1276[LOG-1276])
 
 * Before this update, in the *Logging* dashboard in the {product-title} console, the list of top 10 log-producing containers lacked data points. This update resolves the issue, and the dashboard displays all data points. (link:https://issues.redhat.com/browse/LOG-1353[LOG-1353])
 
 * Before this update, if you were tuning the performance of the Fluentd log forwarder by adjusting the `chunkLimitSize` and `totalLimitSize` values, the `Setting queued_chunks_limit_size for each buffer to` message reported values that were too low. The current update fixes this issue so that this message reports the correct values. (link:https://issues.redhat.com/browse/LOG-1411[LOG-1411])
 
-* Before this update, the Kibana OpenDistro security plugin caused user index migrations to fail. This update resolves the issue by providing a newer version of the plugin. Now, index migrations proceed without errors. (link:https://issues.redhat.com/browse/LOG-1558[LOG-1558])
+* Before this update, the Kibana OpenDistro security plug-in caused user index migrations to fail. This update resolves the issue by providing a newer version of the plug-in. Now, index migrations proceed without errors. (link:https://issues.redhat.com/browse/LOG-1558[LOG-1558])
 
 * Before this update, using a namespace input filter prevented logs in that namespace from appearing in other inputs. With this update, logs are sent to all inputs that can accept them. (link:https://issues.redhat.com/browse/LOG-1570[LOG-1570])
 

modules/builds-understanding-openshift-pipeline.adoc

@@ -14,20 +14,20 @@ Jenkins images on {product-title} are fully supported and users should follow Je
 
 Pipelines give you control over building, deploying, and promoting your applications on {product-title}. Using a combination of the Jenkins Pipeline build strategy, `jenkinsfiles`, and the {product-title} Domain Specific Language (DSL) provided by the Jenkins Client Plug-in, you can create advanced build, test, deploy, and promote pipelines for any scenario.
 
-*{product-title} Jenkins Sync Plugin*
+*{product-title} Jenkins Sync Plug-in*
 
-The {product-title} Jenkins Sync Plugin keeps the build configuration and build objects in sync with Jenkins jobs and builds, and provides the following:
+The {product-title} Jenkins Sync Plug-in keeps the build configuration and build objects in sync with Jenkins jobs and builds, and provides the following:
 
  * Dynamic job and run creation in Jenkins.
  * Dynamic creation of agent pod templates from image streams, image stream tags, or config maps.
  * Injecting of environment variables.
  * Pipeline visualization in the {product-title} web console.
- * Integration with the Jenkins git plugin, which passes commit information from
- * Synchronizing secrets into Jenkins credential entries {product-title} builds to the Jenkins git plugin.
+ * Integration with the Jenkins git plug-in, which passes commit information from
+ * Synchronizing secrets into Jenkins credential entries {product-title} builds to the Jenkins git plug-in.
 
-*{product-title} Jenkins Client Plugin*
+*{product-title} Jenkins Client Plug-in*
 
-The {product-title} Jenkins Client Plugin is a Jenkins plugin which aims to provide a readable, concise, comprehensive, and fluent Jenkins Pipeline syntax for rich interactions with an {product-title} API Server. The plugin uses the {product-title} command line tool, `oc`, which must be available on the nodes executing the script.
+The {product-title} Jenkins Client Plug-in is a Jenkins plug-in which aims to provide a readable, concise, comprehensive, and fluent Jenkins Pipeline syntax for rich interactions with an {product-title} API Server. The plug-in uses the {product-title} command line tool, `oc`, which must be available on the nodes executing the script.
 
 The Jenkins Client Plug-in must be installed on your Jenkins master so the {product-title} DSL will be available to use within the `jenkinsfile` for your application. This plug-in is installed and enabled by default when using the {product-title} Jenkins image.
 

modules/cli-extending-plugins-installing.adoc

@@ -38,7 +38,7 @@ $ oc plugin list
 .Example output
 [source,terminal]
 ----
-The following compatible plugins are available:
+The following compatible plug-ins are available:
 
 /usr/local/bin/<plugin_file>
 ----

modules/cluster-logging-release-notes-5.2.z.adoc

@@ -99,7 +99,7 @@ This release includes link:https://access.redhat.com/errata/RHSA-2021:5127[RHSA-
 
 * Before this update records shipped via syslog would serialize a ruby hash encoding key/value pairs to contain a '=>' character, as well as replace tabs with "#11".  This update serializes the message correctly as proper JSON. (link:https://issues.redhat.com/browse/LOG-1775[LOG-1775])
 
-* Before this update, the Elasticsearch Prometheus exporter plugin compiled index-level metrics using a high-cost query that impacted the Elasticsearch node performance. This update implements a lower-cost query that improves performance. (link:https://issues.redhat.com/browse/LOG-1970[LOG-1970])
+* Before this update, the Elasticsearch Prometheus exporter plug-in compiled index-level metrics using a high-cost query that impacted the Elasticsearch node performance. This update implements a lower-cost query that improves performance. (link:https://issues.redhat.com/browse/LOG-1970[LOG-1970])
 
 * Before this update, Elasticsearch sometimes rejected messages when Log Forwarding was configured with multiple outputs. This happened because configuring one of the outputs modified message content to be a single message. With this update, Log Forwarding duplicates the messages for each output so that output-specific processing does not affect the other outputs. (link:https://issues.redhat.com/browse/LOG-1824[LOG-1824])
 

modules/images-configuration-file.adoc

@@ -54,7 +54,7 @@ status:
 <1> `Image`: Holds cluster-wide information about how to handle images. The canonical, and only valid name is `cluster`.
 <2> `allowedRegistriesForImport`: Limits the container image registries from which normal users may import images. Set this list to the registries that you trust to contain valid images, and that you want applications to be able to import from. Users with permission to create images or `ImageStreamMappings` from the API are not affected by this policy. Typically only cluster administrators have the appropriate permissions.
 <3> `additionalTrustedCA`: A reference to a config map containing additional certificate authorities (CA) that are trusted during image stream import, pod image pull, `openshift-image-registry` pullthrough, and builds. The namespace for this config map is `openshift-config`. The format of the config map is to use the registry hostname as the key, and the PEM certificate as the value, for each additional registry CA to trust.
-<4> `registrySources`: Contains configuration that determines whether the container runtime allows or blocks individual registries when accessing images for builds and pods.  Either the `allowedRegistries` parameter or the `blockedRegistries` parameter can be set, but not both. You can also define whether or not to allow access to insecure registries or registries that allow registries that use image short names. This example uses the `allowedRegistries` parameter, which defines the registries that are allowed to be used. The insecure registry `insecure.com` is also allowed. The `registrySources` paramter does not contain configuration for the internal cluster registry.
+<4> `registrySources`: Contains configuration that determines whether the container runtime allows or blocks individual registries when accessing images for builds and pods.  Either the `allowedRegistries` parameter or the `blockedRegistries` parameter can be set, but not both. You can also define whether or not to allow access to insecure registries or registries that allow registries that use image short names. This example uses the `allowedRegistries` parameter, which defines the registries that are allowed to be used. The insecure registry `insecure.com` is also allowed. The `registrySources` parameter does not contain configuration for the internal cluster registry.
 +
 [NOTE]
 ====

modules/images-other-jenkins-oauth-auth.adoc

@@ -19,7 +19,7 @@ The default {product-title} `admin`, `edit`, and `view` roles and the Jenkins pe
 
 When running Jenkins in an {product-title} pod, the login plug-in looks for a config map named `openshift-jenkins-login-plugin-config` in the namespace that Jenkins is running in.
 
-If this plugin finds and can read in that config map, you can define the role to Jenkins Permission mappings. Specifically:
+If this plug-in finds and can read in that config map, you can define the role to Jenkins Permission mappings. Specifically:
 
  * The login plug-in treats the key and value pairs in the config map as Jenkins permission to {product-title} role mappings.
  * The key is the Jenkins permission group short ID and the Jenkins permission short ID, with those two separated by a hyphen character.

modules/jt-comparison-of-jenkins-and-openshift-pipelines-concepts.adoc

@@ -9,11 +9,11 @@
 You can review and compare the following equivalent terms used in Jenkins and OpenShift Pipelines.
 
 == Jenkins terminology
-Jenkins offers declarative and scripted pipelines that are extensible using shared libraries and plugins. Some basic terms in Jenkins are as follows:
+Jenkins offers declarative and scripted pipelines that are extensible using shared libraries and plug-ins. Some basic terms in Jenkins are as follows:
 
 * *Pipeline*: Automates the entire process of building, testing, and deploying applications by using link:https://groovy-lang.org/[Groovy] syntax.
 * *Node*: A machine capable of either orchestrating or executing a scripted pipeline.
-* *Stage*: A conceptually distinct subset of tasks performed in a pipeline. Plugins or user interfaces often use this block to display the status or progress of tasks.
+* *Stage*: A conceptually distinct subset of tasks performed in a pipeline. Plug-ins or user interfaces often use this block to display the status or progress of tasks.
 * **Step**: A single task that specifies the exact action to be taken, either by using a command or a script.
 
 == OpenShift Pipelines terminology

modules/jt-comparison-of-jenkins-openshift-pipelines-execution-models.adoc

@@ -14,5 +14,5 @@ Jenkins and OpenShift Pipelines offer similar functions but are different in arc
 |Jenkins|OpenShift Pipelines
 |Jenkins has a controller node. Jenkins runs pipelines and steps centrally, or orchestrates jobs running in other nodes.|OpenShift Pipelines is serverless and distributed, and there is no central dependency for execution.
 |Containers are launched by the Jenkins controller node through the pipeline.|OpenShift Pipelines adopts a 'container-first' approach, where every step runs as a container in a pod (equivalent to nodes in Jenkins).
-|Extensibility is achieved by using plugins.|Extensibility is achieved by using tasks in Tekton Hub or by creating custom tasks and scripts.
+|Extensibility is achieved by using plug-ins.|Extensibility is achieved by using tasks in Tekton Hub or by creating custom tasks and scripts.
 |===

modules/jt-examples-of-common-use-cases.adoc

@@ -9,7 +9,7 @@
 Both Jenkins and OpenShift Pipelines offer capabilities for common CI/CD use cases, such as:
 
 * Compiling, building, and deploying images using Apache Maven
-* Extending the core capabilities by using plugins
+* Extending the core capabilities by using plug-ins
 * Reusing shareable libraries and custom scripts
 
 == Running a Maven pipeline in Jenkins and OpenShift Pipelines
@@ -151,12 +151,12 @@ spec:
 
 ----
 
-== Extending the core capabilities of Jenkins and OpenShift Pipelines by using plugins
-Jenkins has the advantage of a large ecosystem of numerous plugins developed over the years by its extensive user base. You can search and browse the plugins in the link:https://plugins.jenkins.io/[Jenkins Plugin Index].
+== Extending the core capabilities of Jenkins and OpenShift Pipelines by using plug-ins
+Jenkins has the advantage of a large ecosystem of numerous plug-ins developed over the years by its extensive user base. You can search and browse the plug-ins in the link:https://plugins.jenkins.io/[Jenkins Plug-in Index].
 
 OpenShift Pipelines also has many tasks developed and contributed by the community and enterprise users. A publicly available catalog of reusable OpenShift Pipelines tasks are available in the link:https://hub.tekton.dev/[Tekton Hub].
 
-In addition, OpenShift Pipelines incorporates many of the plugins of the Jenkins ecosystem within its core capabilities. For example, authorization is a critical function in both Jenkins and OpenShift Pipelines. While Jenkins ensures authorization using the link:https://plugins.jenkins.io/role-strategy/[Role-based Authorization Strategy] plugin, OpenShift Pipelines uses OpenShift's built-in Role-based Access Control system.
+In addition, OpenShift Pipelines incorporates many of the plug-ins of the Jenkins ecosystem within its core capabilities. For example, authorization is a critical function in both Jenkins and OpenShift Pipelines. While Jenkins ensures authorization using the link:https://plugins.jenkins.io/role-strategy/[Role-based Authorization Strategy] plug-in, OpenShift Pipelines uses OpenShift's built-in Role-based Access Control system.
 
 == Sharing reusable code in Jenkins and OpenShift Pipelines
 Jenkins link:https://www.jenkins.io/doc/book/pipeline/shared-libraries/[shared libraries] provide reusable code for parts of Jenkins pipelines. The libraries are shared between link:https://www.jenkins.io/doc/book/pipeline/jenkinsfile/[Jenkinsfiles] to create highly modular pipelines without code repetition.

modules/jt-migrating-from-jenkins-plugins-to-openshift-pipelines-hub-tasks.adoc

@@ -5,11 +5,11 @@
 :_content-type: PROCEDURE
 
 [id="jt-migrating-from-jenkins-plugins-to-openshift-pipelines-hub-tasks_{context}"]
-= Migrating from Jenkins plugins to Tekton Hub tasks
+= Migrating from Jenkins plug-ins to Tekton Hub tasks
 
-You can extend the capability of Jenkins by using link:https://plugins.jenkinsci.org[plugins]. To achieve similar extensibility in OpenShift Pipelines, use any of the tasks available from link:https://hub.tekton.dev[Tekton Hub].
+You can extend the capability of Jenkins by using link:https://plugins.jenkinsci.org[plug-ins]. To achieve similar extensibility in OpenShift Pipelines, use any of the tasks available from link:https://hub.tekton.dev[Tekton Hub].
 
-For example, consider the link:https://hub.tekton.dev/tekton/task/git-clone[git-clone] task in Tekton Hub, which corresponds to the link:https://plugins.jenkins.io/git/[git plugin] for Jenkins.
+For example, consider the link:https://hub.tekton.dev/tekton/task/git-clone[git-clone] task in Tekton Hub, which corresponds to the link:https://plugins.jenkins.io/git/[git plug-in] for Jenkins.
 
 .Example: `git-clone` task from Tekton Hub
 [source,yaml,subs="attributes+"]