Merge pull request #34668 from jboxman/use-ascii-apostrophe

Use ASCII ' instead of ’ for apostrophe

Author: jboxman

architecture/architecture.adoc

@@ -25,7 +25,7 @@ workflows.
 * xref:../registry/architecture-component-imageregistry.adoc[Image Registry] -
 The image registry provides a scalable repository for storing and retrieving
 container images that are produced by and run on the cluster. Image access is
-integrated with the cluster’s role-based access controls and user authentication
+integrated with the cluster's role-based access controls and user authentication
 system.
 * xref:../openshift_images/images-understand.adoc[Image
 streams] - The imagestream API provides an abstraction over container images

architecture/cicd_gitops.adoc

@@ -13,7 +13,7 @@ Using a _continuous integration/continuous delivery_ (CI/CD) methodology enables
 _Continuous integration_ is an automation process for developers. Code changes to an application are regularly built, tested, and merged to a shared repository.
 
 _Continuous delivery_ and _continuous deployment_ are closely related concepts that are sometimes used interchangeably and refer to automation of the pipeline.
-Continuous delivery uses automation to ensure that a developer’s changes to an application are tested and sent to a repository, where an operations team can deploy them to a production environment. Continuous deployment enables the release of changes, starting from the repository and ending in production. Continuous deployment speeds up application delivery and prevents the operations team from getting overloaded.
+Continuous delivery uses automation to ensure that a developer's changes to an application are tested and sent to a repository, where an operations team can deploy them to a production environment. Continuous deployment enables the release of changes, starting from the repository and ending in production. Continuous deployment speeds up application delivery and prevents the operations team from getting overloaded.
 
 [id="cicd_gitops_methodology"]
 == The GitOps methodology and practice

architecture/understanding-development.adoc

@@ -378,7 +378,7 @@ like updating the Operator, can happen automatically and invisibly to the
 Operator's users.
 
 An example of a useful Operator is one that is set up to automatically back up
-data at particular times. Having an Operator manage an application’s backup at
+data at particular times. Having an Operator manage an application's backup at
 set times can save a system administrator from remembering to do it.
 
 Any application maintenance that has traditionally been completed manually,

cicd/gitops/gitops-release-notes.adoc

@@ -20,7 +20,7 @@ For an overview of {gitops-title}, see xref:../../cicd/gitops/understanding-open
 [id="gitops-inclusive-language"]
 == Making open source more inclusive
 
-Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see link:https://www.redhat.com/en/blog/making-open-source-more-inclusive-eradicating-problematic-language[Red Hat CTO Chris Wright’s message].
+Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see link:https://www.redhat.com/en/blog/making-open-source-more-inclusive-eradicating-problematic-language[Red Hat CTO Chris Wright's message].
 
 // Modules included, most to least recent
 include::modules/gitops-release-notes-1-1.adoc[leveloffset=+1]

cicd/pipelines/op-release-notes.adoc

@@ -21,7 +21,7 @@ For an overview of {pipelines-title}, see xref:../../cicd/pipelines/understandin
 [id="openshift-pipelines-inclusive-language"]
 == Making open source more inclusive
 
-Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see link:https://www.redhat.com/en/blog/making-open-source-more-inclusive-eradicating-problematic-language[Red Hat CTO Chris Wright’s message].
+Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see link:https://www.redhat.com/en/blog/making-open-source-more-inclusive-eradicating-problematic-language[Red Hat CTO Chris Wright's message].
 
 // Modules included, most to least recent
 include::modules/op-release-notes-1-4.adoc[leveloffset=+1]

jaeger/jaeger_install/rhbjaeger-deploying.adoc

@@ -72,7 +72,7 @@ include::modules/jaeger-config-ingester.adoc[leveloffset=+2]
 [id="injecting-sidecars"]
 == Injecting sidecars
 
-{ProductName} relies on a proxy sidecar within the application’s pod to provide the agent. The Jaeger Operator can inject Jaeger Agent sidecars into Deployment workloads. You can enable automatic sidecar injection or manage it manually.
+{ProductName} relies on a proxy sidecar within the application's pod to provide the agent. The Jaeger Operator can inject Jaeger Agent sidecars into Deployment workloads. You can enable automatic sidecar injection or manage it manually.
 
 include::modules/jaeger-sidecar-automatic.adoc[leveloffset=+2]
 

jaeger/jaeger_install/rhbjaeger-updating.adoc

@@ -9,4 +9,4 @@ The Operator Lifecycle Manager (OLM) controls the installation, upgrade, and rol
 The OLM queries for available Operators as well as upgrades for installed Operators.
 For more information about how {product-title} handled upgrades, refer to the xref:../../operators/understanding/olm/olm-understanding-olm.adoc#olm-understanding-olm[Operator Lifecycle Manager] documentation.
 
-The update approach used by the Jaeger Operator upgrades the managed Jaeger instances to the version associated with the Operator. Whenever a new version of the Jaeger Operator is installed, all the Jaeger application instances managed by the Operator will be upgraded to the Operator’s  version.  For example, if version 1.10 is installed (both Operator and backend components) and the Operator is upgraded to version 1.11, then as soon as the Operator upgrade has completed, the Operator will scan for running Jaeger instances and upgrade them to 1.11 as well.
+The update approach used by the Jaeger Operator upgrades the managed Jaeger instances to the version associated with the Operator. Whenever a new version of the Jaeger Operator is installed, all the Jaeger application instances managed by the Operator will be upgraded to the Operator's  version.  For example, if version 1.10 is installed (both Operator and backend components) and the Operator is upgraded to version 1.11, then as soon as the Operator upgrade has completed, the Operator will scan for running Jaeger instances and upgrade them to 1.11 as well.

logging/cluster-logging-release-notes.adoc

@@ -19,7 +19,7 @@ The following advisories are available for {ProductName} 5.0:
 [id="openshift-logging-5-0-inclusive-language"]
 == Making open source more inclusive
 
-Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see link:https://www.redhat.com/en/blog/making-open-source-more-inclusive-eradicating-problematic-language[Red Hat CTO Chris Wright’s message].
+Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see link:https://www.redhat.com/en/blog/making-open-source-more-inclusive-eradicating-problematic-language[Red Hat CTO Chris Wright's message].
 
 [id="openshift-logging-5-0-deprecated-removed-features"]
 == Deprecated and removed features

modules/architecture-platform-benefits.adoc

@@ -20,7 +20,7 @@ endif::[]
 ifdef::openshift-dedicated[]
 * {product-title} clusters are deployed on AWS environments and can be used as part of a hybrid approach for application management.
 endif::[]
-* Integrated Red Hat technology. Major components in {product-title} come from {op-system-base-full} and related Red Hat technologies. {product-title} benefits from the intense testing and certification initiatives for Red Hat’s enterprise quality software.
+* Integrated Red Hat technology. Major components in {product-title} come from {op-system-base-full} and related Red Hat technologies. {product-title} benefits from the intense testing and certification initiatives for Red Hat's enterprise quality software.
 * Open source development model. Development is completed in the open, and the source code is available from public software repositories. This open collaboration fosters rapid innovation and development.
 
 Although Kubernetes excels at managing your applications, it does not specify

modules/builds-secrets-overview.adoc

@@ -22,7 +22,7 @@ data: <2>
 stringData: <4>
   hostname: myapp.mydomain.com <5>
 ----
-<1> Indicates the structure of the secret’s key names and values.
+<1> Indicates the structure of the secret's key names and values.
 <2> The allowable format for the keys in the `data` field must meet the guidelines in the `DNS_SUBDOMAIN` value in the Kubernetes identifiers glossary.
 <3> The value associated with keys in the `data` map must be base64 encoded.
 <4> Entries in the `stringData` map are converted to base64 and the entry are then moved to the `data` map automatically. This field is write-only. The value is only be returned by the `data` field.