Merge pull request #9266 from kalexand-rh/enterprise-3.7

removing please

Author: kalexand-rh

README.adoc

@@ -1,3 +1,3 @@
 = OpenShift Documentation
 
-Welcome to the OpenShift documentation GitHub repository. To contribute to OpenShift docs, please refer to: https://github.com/openshift/openshift-docs/blob/master/README.adoc
+Welcome to the OpenShift documentation GitHub repository. To contribute to OpenShift docs, see https://github.com/openshift/openshift-docs/blob/master/README.adoc

admin_guide/index.adoc

@@ -29,7 +29,7 @@ performed only by the OpenShift Operations Team. They are included in this
 guide for informational purposes to help you as an {product-title} cluster
 administrator better understand what configuration options are possible. If you
 would like to request a change to your cluster that you cannot perform using the
-administrator CLI, please open a support case on the
+administrator CLI, open a support case on the
 https://access.redhat.com/support/[Red Hat Customer Portal]._
 ====
 

admin_guide/manage_scc.adoc

@@ -476,7 +476,7 @@ $ oc edit scc restricted
 === Ensure That Admission Attempts to Use a Specific SCC First
 
 You may control the sort ordering of SCCs in admission by setting the `Priority`
-field of the SCCs.  Please see the
+field of the SCCs. See the
 xref:../architecture/additional_concepts/authorization.adoc#scc-prioritization[SCC
 Prioritization] section for more information on sorting.
 

admin_guide/osd_request.adoc

@@ -6,6 +6,6 @@ performed by the {product-title} Operations Team. They are included in this guid
 informational purposes to help you as an {product-title} cluster administrator
 better understand what configuration options are possible. If you would like to
 request a change to your cluster that you cannot perform using the
-administrator CLI, please open a support case on the
+administrator CLI, open a support case on the
 https://access.redhat.com/support/[Red Hat Customer Portal]._
 ====

admin_guide/sdn_troubleshooting.adoc

@@ -116,8 +116,8 @@ Trying 1.2.3.4...
 telnet: connect to address 1.2.3.4: Connection refused
 ....
 
-Which tells us that the router is not listening on that port.  Please
-see the <<debugging-the-router>> section for more pointers on how to
+Which tells us that the router is not listening on that port.  See the 
+<<debugging-the-router>> section for more pointers on how to
 configure the router.
 
 
@@ -165,7 +165,7 @@ HostIP: 192.168.122.202   PodIP: 10.128.0.4
 ....
 
 You should see the host IP that corresponds to your external address.
-If you do not, please refer to the
+If you do not, refer to the
 xref:../architecture/networking/routes.adoc#architecture-core-concepts-routes[router documentation] to
 configure the router pod to run on the right node (by setting the
 affinity correctly) or update your DNS to match the IP addresses where
@@ -190,7 +190,7 @@ xref:../architecture/networking/routes.adoc#architecture-core-concepts-routes[ro
 
 If your route is present, then you need to debug access to the
 endpoints.  That's the same as if you were debugging problems with a
-service, so please continue on with the next <<debugging-a-service>>
+service, so continue on with the next <<debugging-a-service>>
 section.
 
 [[debugging-a-service]]
@@ -456,7 +456,7 @@ node).
 and flows matching `nw_src=<pod_IP_address>` and `nw_dst=<pod_IP_address>` (for
 incoming and outgoing IP traffic for that pod).
 
-If there are flows missing, please look in the <<reading-the-logs>>
+If there are flows missing, look in the <<reading-the-logs>>
 section.
 
 ==== Is the `iptables` configuration correct?

architecture/core_concepts/builds_and_image_streams.adoc

@@ -161,7 +161,7 @@ even if all Pipeline build configurations are deleted.
 It must be manually deleted by the user.
 ====
 
-For more information about Jenkins Pipelines, please see the
+For more information about Jenkins Pipelines, see the
 link:https://jenkins.io/doc/pipeline/[Jenkins documentation].
 
 endif::[]

getting_started/dedicated_administrators.adoc

@@ -25,7 +25,7 @@ operations.
 While your account does have these increased permissions, the actual cluster
 maintenance and host configuration is still performed by the OpenShift
 Operations Team. If you would like to request a change to your cluster that you
-cannot perform using the administrator CLI, please open a support case on the
+cannot perform using the administrator CLI, open a support case on the
 https://access.redhat.com/support/[Red Hat Customer Portal].
 ====
 
@@ -137,7 +137,7 @@ $ oc adm groups remove-users dedicated-admins <user_name>
 ----
 
 If this group is currently empty or if you need assistance editing group
-membership, please open a support case on the
+membership, open a support case on the
 link:https://access.redhat.com/support/[Red Hat Customer Portal].
 
 [[gs-dedicated-admin-granting-permissions]]
@@ -178,7 +178,7 @@ ranges] on other projects. This allows you to better constrain how compute
 resources and objects are consumed by users across the cluster.
 
 Defaults can be set for quotas and limit ranges for new projects at creation. To
-request such a change, please open a support case on the
+request such a change, open a support case on the
 https://access.redhat.com/support/[Red Hat Customer Portal].
 
 [[gs-dedicated-admin-whats-next]]

getting_started/devpreview_faq.adoc

@@ -111,7 +111,7 @@ If you would like to ask a larger group of people for help, including
 {product-title} users, engineers, and operations team members, you can ask a
 question using the
 https://groups.google.com/forum/#!forum/openshift[{product-title} Forums].
-Please make sure to use the "dev-preview" tag when creating a new post.
+Make sure to use the "dev-preview" tag when creating a new post.
 
 WHAT SHOULD I DO WHEN I FIND A BUG?::
 Red Hat's Bugzilla instance can be used to

install_config/aggregate_logging.adoc

@@ -3398,7 +3398,7 @@ Namespace for oVirt engine related metadata. The FQDN of the oVirt engine is
 [[exported-fields-aushape]]
 === Aushape Fields
 
-Audit events converted with Aushape. For more information please see
+Audit events converted with Aushape. For more information, see
 link:https://github.com/Scribery/aushape[Aushape].
 
 [cols="3,7",options="header"]
@@ -3456,7 +3456,7 @@ Parsed audit event data related to Aushape.
 [[exported-fields-tlog]]
 === Tlog Fields
 
-Tlog terminal I/O recording messages. For more information please see
+Tlog terminal I/O recording messages. For more information see
 link:https://github.com/Scribery/tlog[Tlog].
 
 [cols="3,7",options="header"]

install_config/cluster_metrics.adoc

@@ -52,7 +52,7 @@ donut chart displays usage against the resource limit. For example: `145
 Available of 200 MiB`, with the donut chart showing `55 MiB Used`.
 
 ifdef::openshift-origin[]
-For more information about the metrics integration, please refer to the
+For more information about the metrics integration, refer to the
 link:https://github.com/openshift/origin-metrics[Origin Metrics] GitHub project.
 endif::[]
 
@@ -585,7 +585,7 @@ The `hawkular-metrics.pem` value needs to contain the certificate in its *_.pem_
 format. You may also need to provide the certificate for the Certificate Authority
 which signed this *_pem_* file via the `hawkular-metrics-ca.cert` secret.
 
-For more information, please see the
+For more information, see the
 xref:../architecture/networking/routes.adoc#secured-routes[re-encryption
 route documentation].
 
@@ -759,7 +759,7 @@ $ curl -H "Authorization: Bearer XXXXXXXXXXXXXXXXX" \
        -X GET https://${KUBERNETES_MASTER}/api/v1/proxy/namespaces/openshift-infra/services/https:heapster:/validate
 ----
 
-For more information about Heapster and how to access its APIs, please refer the
+For more information about Heapster and how to access its APIs, refer the
 link:https://github.com/kubernetes/heapster/[Heapster] project.
 endif::[]
 

install_config/configuring_pipeline_execution.adoc

@@ -91,8 +91,8 @@ interactions with an OpenShift API Server. The plugin leverages the OpenShift
 command line tool (`oc`) which must be available on the nodes executing the
 script.
 
-For more information about installing and configuring the plugin, please use the links
-provided below which reference the official documentation.
+For more information about installing and configuring the plugin, use the links
+provided below that reference the official documentation.
 
 * https://github.com/openshift/jenkins-client-plugin/blob/master/README.md#installing[Installing]
 * https://github.com/openshift/jenkins-client-plugin/blob/master/README.md#configuring-an-openshift-cluster[Configuring an OpenShift Cluster]

install_config/install/advanced_install.adoc

@@ -2563,7 +2563,7 @@ required so that the container can read the SSH key under
 its restricted SELinux context. This also means that your
 original SSH key file will be re-labeled to something like
 `system_u:object_r:container_file_t:s0:c113,c247`. For more details
-about `:Z` please check the `docker-run(1)` man page. Keep this in mind
+about `:Z`, check the `docker-run(1)` man page. Keep this in mind
 when providing these volume mount specifications because this might
 have unexpected consequences: for example, if you mount (and therefore
 re-label) your whole `$HOME/.ssh` directory it will block the host's

install_config/persistent_storage/persistent_storage_glusterfs.adoc

@@ -572,7 +572,7 @@ $ sudo setsebool -P virt_sandbox_use_fusefs on
 [NOTE]
 ====
 The `virt_sandbox_use_fusefs` boolean is defined by the *docker-selinux*
-package. If you get an error saying it is not defined, please ensure that this
+package. If you get an error saying it is not defined, ensure that this
 package is installed.
 ====
 

install_config/registry/extended_registry_configuration.adoc

@@ -490,7 +490,7 @@ middleware.
 <3> The CloudFront base URL. In the AWS management console, this is listed as
 *Domain Name* of CloudFront distribution.
 <4> The location of your AWS private key on the filesystem. This must be not
-confused with Amazon EC2 key pair. Please refer to
+confused with Amazon EC2 key pair. See the
 link:http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-trusted-signers.html#private-content-creating-cloudfront-key-pairs[AWS
 documentation] on creating CloudFront key pairs for your trusted signers. The
 file needs to be mounted as a xref:../../dev_guide/secrets.adoc#dev-guide-secrets[secret] into the registry

release_notes/ocp_3_3_release_notes.adoc

@@ -1232,12 +1232,12 @@ This bug is fixed in {product-title} 3.3 by not relying on image streams and dep
 * Previously, a bug in a script which cleans out all pre-existing images and containers during a *docker* 1.10 upgrade would cause the script to miss some images with name and tag *none*, potentially resulting in a slower or failed *docker* upgrade. This script has been updated to use a more robust method of clean-up which also catches orphaned images. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1351406[*BZ#1351406*])
 
 * Previously, nodes had their schedulability state reset to the state defined in the inventory used during an upgrade. If the scheduling state had been modified since the inventory file was created, this would be a surprise to administrators. The upgrade process has been modified to preserve the current schedulability state during upgrade so that nodes do not change state after an upgrade. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1372594[*BZ#1372594*])
-
+S
 [[ocp-33-technology-preview]]
 == Technology Preview Features
 
 Some features in this release are currently in Technology Preview. These
-experimental features are not intended for production use. Please note the
+experimental features are not intended for production use. Note the
 following scope of support on the Red Hat Customer Portal for these features:
 
 https://access.redhat.com/support/offerings/techpreview[Technology Preview

release_notes/ocp_3_4_release_notes.adoc

@@ -843,7 +843,7 @@ This fix addresses the JavaScript bug and the HTML page is refreshed after delet
 == Technology Preview Features
 
 Some features in this release are currently in Technology Preview. These
-experimental features are not intended for production use. Please note the
+experimental features are not intended for production use. Note the
 following scope of support on the Red Hat Customer Portal for these features:
 
 https://access.redhat.com/support/offerings/techpreview[Technology Preview

release_notes/ocp_3_5_release_notes.adoc

@@ -1639,7 +1639,7 @@ even if mount was in flight when deletion request is received.
 == Technology Preview Features
 
 Some features in this release are currently in Technology Preview. These
-experimental features are not intended for production use. Please note the
+experimental features are not intended for production use. Note the
 following scope of support on the Red Hat Customer Portal for these features:
 
 https://access.redhat.com/support/offerings/techpreview[Technology Preview

release_notes/ocp_3_6_release_notes.adoc

@@ -2410,7 +2410,7 @@ version as docker-registry. This issue is now fixed.
 == Technology Preview Features
 
 Some features in this release are currently in Technology Preview. These
-experimental features are not intended for production use. Please note the
+experimental features are not intended for production use. Note the
 following scope of support on the Red Hat Customer Portal for these features:
 
 https://access.redhat.com/support/offerings/techpreview[Technology Preview

release_notes/ocp_3_7_release_notes.adoc

@@ -1106,7 +1106,7 @@ When `openshift_installer` is run for logging to upgrade to 3.7, the installer
 now checks for `ES_COPY` in the inventory and fails the upgrade with:
 
 ----
-msg: The ES_COPY feature is no longer supported. Please remove the variable from your inventory
+msg: The ES_COPY feature is no longer supported. Remove the variable from your inventory
 ----
 
 See
@@ -2823,7 +2823,7 @@ failed health checks. This bug fix sets the `any_errors_fatal` play option to
 == Technology Preview Features
 
 Some features in this release are currently in Technology Preview. These
-experimental features are not intended for production use. Please note the
+experimental features are not intended for production use. Note the
 following scope of support on the Red Hat Customer Portal for these features:
 
 https://access.redhat.com/support/offerings/techpreview[Technology Preview

release_notes/ose_3_1_release_notes.adoc

@@ -262,7 +262,7 @@ https://bugzilla.redhat.com/show_bug.cgi?id=1278648[BZ#1278648]:: If, when upgra
 == Technology Preview Features
 
 Some features in this release are currently in Technology Preview. These
-experimental features are not intended for production use. Please note the
+experimental features are not intended for production use. Note the
 following scope of support on the Red Hat Customer Portal for these features:
 
 https://access.redhat.com/support/offerings/techpreview[Technology Preview

release_notes/ose_3_2_release_notes.adoc

@@ -598,7 +598,7 @@ The default values for pod networking have changed:
 
 - Due to a change in the upstream JSON serialization path used in Kubernetes, some
 fields that were previously accepted case-insensitively are no longer accepted.
-Please validate that your API objects have the correct case for all attributes.
+Validate that your API objects have the correct case for all attributes.
 - When creating a deployment configuration, omitting the `*spec.selector*` field
 will default that value to the pod template labels.
 - `*ImageStreamTag*` objects now return the spec tag `tag`, the current status
@@ -730,7 +730,7 @@ session affinity.
 == Technology Preview Features
 
 Some features in this release are currently in Technology Preview. These
-experimental features are not intended for production use. Please note the
+experimental features are not intended for production use. Note the
 following scope of support on the Red Hat Customer Portal for these features:
 
 https://access.redhat.com/support/offerings/techpreview[Technology Preview
@@ -1347,7 +1347,7 @@ identify these configurations and allow new nodes to be added as expected.
 https://bugzilla.redhat.com/show_bug.cgi?id=1356463[*BZ#1356463*]::
 If Docker 1.8.2 is installed on a host before starting an OpenShift Enterprise
 3.2 installation, Ansible now reports the following message: "Cannot upgrade
-Docker to greater than or equal to 1.10, please upgrade or remove Docker
+Docker to greater than or equal to 1.10, upgrade or remove Docker
 manually, or use the Docker upgrade playbook if OpenShift is already installed."
 
 https://bugzilla.redhat.com/show_bug.cgi?id=1316378[*BZ#1316378*]::

rest_api/api/v1.Binding.adoc

@@ -11,7 +11,7 @@ toc::[]
 
 == Description
 [%hardbreaks]
-Binding ties one object to another; for example, a pod is bound to a node by a scheduler. Deprecated in 1.7, please use the bindings subresource of pods instead.
+Binding ties one object to another; for example, a pod is bound to a node by a scheduler. Deprecated in 1.7. Use the bindings subresource of pods instead.
 
 == Object Schema
 Expand or mouse-over a field for more information about it.
@@ -247,6 +247,3 @@ EOF
 * application/json
 * application/yaml
 * application/vnd.kubernetes.protobuf
-
-
-

scaling_performance/host_practices.adoc

@@ -74,7 +74,7 @@ Version 3 of etcd implements a backwards compatible storage API that facilitates
 etcd schema migration will be required by future {product-title} upgrades.
 ====
 
-In addition to changing the storage mode for new installs to v3, {product-title} 3.6 also begins enforcing _quorum reads_ for all {product-title} types. This is done to ensure that queries against etcd do not return stale data. In single-node etcd clusters, stale data is not a concern. In highly available etcd deployments typically found in production clusters, quorum reads ensure valid query results. A quorum read is _linearizable_ in database terms - every client sees the latest updated state of the cluster, and all clients see the same sequence of reads and writes. Please see the etcd 3.1 link:https://coreos.com/blog/etcd-3-1-announcement.html[announcement] for more information on performance improvements.
+In addition to changing the storage mode for new installs to v3, {product-title} 3.6 also begins enforcing _quorum reads_ for all {product-title} types. This is done to ensure that queries against etcd do not return stale data. In single-node etcd clusters, stale data is not a concern. In highly available etcd deployments typically found in production clusters, quorum reads ensure valid query results. A quorum read is _linearizable_ in database terms - every client sees the latest updated state of the cluster, and all clients see the same sequence of reads and writes. See the etcd 3.1 link:https://coreos.com/blog/etcd-3-1-announcement.html[announcement] for more information on performance improvements.
 
 It is important to note that {product-title} uses etcd for storing additional information beyond what Kubernetes itself requires. For example, {product-title} stores information about images, builds, and other components in etcd, as is required by features that {product-title} adds on top of Kubernetes. Ultimately, this means that guidance around performance and sizing for etcd hosts will differ from Kubernetes and other recommendations in salient ways. Red Hat tests etcd scalability and performance with the {product-title} use-case and parameters in mind to generate the most accurate recommendations.
 

whats_new/ose_3_0_release_notes.adoc

@@ -65,7 +65,7 @@ previous versions will be provided in future releases.
 == Technology Preview Features
 
 Some features in this release are currently in Technology Preview. These
-experimental features are not intended for production use. Please note the
+experimental features are not intended for production use. Note the
 following scope of support on the Red Hat Customer Portal for these features:
 
 https://access.redhat.com/support/offerings/techpreview[Technology Preview