Tweak page production environment

This page has a lot of indentations or line wrappings that are "wrong".
It would make tracking changes (especially for localization teams) very
difficult.

content/en/docs/setup/production-environment/_index.md

@@ -221,9 +221,21 @@ Using plugins, the apiserver can leverage your organization’s existing
   authentication methods, such as LDAP or Kerberos. See
   [Authentication](/docs/reference/access-authn-authz/authentication/)
   for a description of these different methods of authenticating Kubernetes users.
-- *Authorization*: When you set out to authorize your regular users, you will probably choose between RBAC and ABAC authorization. See [Authorization Overview](/docs/reference/access-authn-authz/authorization/) to review different modes for authorizing user accounts (as well as service account access to your cluster):
+- *Authorization*: When you set out to authorize your regular users, you will probably choose
-  - *Role-based access control* ([RBAC](/docs/reference/access-authn-authz/rbac/)): Lets you assign access to your cluster by allowing specific sets of permissions to authenticated users. Permissions can be assigned for a specific namespace (Role) or across the entire cluster (ClusterRole). Then using RoleBindings and ClusterRoleBindings, those permissions can be attached to particular users.
+  between RBAC and ABAC authorization. See [Authorization Overview](/docs/reference/access-authn-authz/authorization/)
-  - *Attribute-based access control* ([ABAC](/docs/reference/access-authn-authz/abac/)): Lets you create policies based on resource attributes in the cluster and will allow or deny access based on those attributes. Each line of a policy file identifies versioning properties (apiVersion and kind) and a map of spec properties to match the subject (user or group), resource property, non-resource property (/version or /apis), and readonly. See [Examples](/docs/reference/access-authn-authz/abac/#examples) for details.
+  to review different modes for authorizing user accounts (as well as service account access to
+  your cluster):
+  - *Role-based access control* ([RBAC](/docs/reference/access-authn-authz/rbac/)): Lets you
+    assign access to your cluster by allowing specific sets of permissions to authenticated users.
+    Permissions can be assigned for a specific namespace (Role) or across the entire cluster
+    (ClusterRole). Then using RoleBindings and ClusterRoleBindings, those permissions can be attached
+    to particular users.
+  - *Attribute-based access control* ([ABAC](/docs/reference/access-authn-authz/abac/)): Lets you
+    create policies based on resource attributes in the cluster and will allow or deny access
+    based on those attributes. Each line of a policy file identifies versioning properties (apiVersion
+    and kind) and a map of spec properties to match the subject (user or group), resource property,
+    non-resource property (/version or /apis), and readonly. See
+    [Examples](/docs/reference/access-authn-authz/abac/#examples) for details.
 
 As someone setting up authentication and authorization on your production Kubernetes cluster, here are some things to consider:
 
@@ -268,8 +280,12 @@ do on a cluster, while a service account defines pod access within a particular
   namespace. By default, a pod takes on the default service account from its namespace.
   See [Managing Service Accounts](/docs/reference/access-authn-authz/service-accounts-admin/)
   for information on creating a new service account. For example, you might want to:
-  - Add secrets that a pod could use to pull images from a particular container registry. See [Configure Service Accounts for Pods](/docs/tasks/configure-pod-container/configure-service-account/) for an example.
+  - Add secrets that a pod could use to pull images from a particular container registry. See
-  - Assign RBAC permissions to a service account. See [ServiceAccount permissions](/docs/reference/access-authn-authz/rbac/#service-account-permissions) for details.
+    [Configure Service Accounts for Pods](/docs/tasks/configure-pod-container/configure-service-account/)
+    for an example.
+  - Assign RBAC permissions to a service account. See
+    [ServiceAccount permissions](/docs/reference/access-authn-authz/rbac/#service-account-permissions)
+    for details.
 
 ## {{% heading "whatsnext" %}}
 
@@ -282,7 +298,9 @@ and set up high availability for features such as
   [etcd](/docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm/)
   and the
   [API server](/docs/setup/production-environment/tools/kubeadm/ha-topology/).
-- Choose from [kubeadm](/docs/setup/production-environment/tools/kubeadm/), [kops](/docs/setup/production-environment/tools/kops/) or [Kubespray](/docs/setup/production-environment/tools/kubespray/)
+- Choose from [kubeadm](/docs/setup/production-environment/tools/kubeadm/),
+  [kops](/docs/setup/production-environment/tools/kops/) or
+  [Kubespray](/docs/setup/production-environment/tools/kubespray/)
   deployment methods.
 - Configure user management by determining your
   [Authentication](/docs/reference/access-authn-authz/authentication/) and
@@ -291,3 +309,4 @@ deployment methods.
   [resource limits](/docs/tasks/administer-cluster/manage-resources/),
   [DNS autoscaling](/docs/tasks/administer-cluster/dns-horizontal-autoscaling/)
   and [service accounts](/docs/reference/access-authn-authz/service-accounts-admin/).
+