Revert Latin phrases to original form

content/en/docs/concepts/extend-kubernetes/api-extension/custom-resources.md

@@ -81,7 +81,7 @@ Signs that your API might not be declarative include:
  - The client says "do this", and then gets a synchronous response back when it is done.
  - The client says "do this", and then gets an operation ID back, and has to check a separate Operation object to determine completion of the request.
  - You talk about Remote Procedure Calls (RPCs).
- - Directly storing large amounts of data (e.g. > a few kB per object, or >1000s of objects).
+ - Directly storing large amounts of data (For example, > a few kB per object, or >1000s of objects).
  - High bandwidth access (10s of requests per second sustained) needed.
  - Store end-user data (such as images, PII, etc.) or other large-scale data processed by applications.
  - The natural operations on the objects are not CRUD-y.
@@ -105,7 +105,7 @@ Use a [secret](/docs/concepts/configuration/secret/) for sensitive data, which i
 Use a custom resource (CRD or Aggregated API) if most of the following apply:
 
 * You want to use Kubernetes client libraries and CLIs to create and update the new resource.
-* You want top-level support from `kubectl` (e.g. `kubectl get my-object object-name`).
+* You want top-level support from `kubectl` (For example, `kubectl get my-object object-name`).
 * You want to build new automation that watches for updates on the new object, and then CRUD other objects, or vice versa.
 * You want to write automation that handles updates to the object.
 * You want to use Kubernetes API conventions like `.spec`, `.status`, and `.metadata`.
@@ -174,14 +174,14 @@ CRDs are easier to create than Aggregated APIs.
 
 ### Advanced features and flexibility
 
-Aggregated APIs offer more advanced API features and customization of other features; e.g. the storage layer.
+Aggregated APIs offer more advanced API features and customization of other features; for example, the storage layer.
 
 | Feature | Description | CRDs | Aggregated API |
 | ------- | ----------- | ---- | -------------- |
 | Validation | Help users prevent errors and allow you to evolve your API independently of your clients. These features are most useful when there are many clients who can't all update at the same time. | Yes.  Most validation can be specified in the CRD using [OpenAPI v3.0 validation](/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/#validation).  Any other validations supported by addition of a [Validating Webhook](/docs/reference/access-authn-authz/admission-controllers/#validatingadmissionwebhook-alpha-in-1-8-beta-in-1-9). | Yes, arbitrary validation checks |
 | Defaulting | See above | Yes, either via [OpenAPI v3.0 validation](/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/#defaulting) `default` keyword (GA in 1.17), or via a [Mutating Webhook](/docs/reference/access-authn-authz/admission-controllers/#mutatingadmissionwebhook) (though this will not be run when reading from etcd for old objects). | Yes |
 | Multi-versioning | Allows serving the same object through two API versions. Can help ease API changes like renaming fields. Less important if you control your client versions. | [Yes](/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definition-versioning) | Yes |
-| Custom Storage | If you need storage with a different performance mode (e.g. time-series database instead of key-value store) or isolation for security (e.g. encryption secrets or different | No | Yes |
+| Custom Storage | If you need storage with a different performance mode (For example, time-series database instead of key-value store) or isolation for security (For example, encryption secrets or different) | No | Yes |
 | Custom Business Logic | Perform arbitrary checks or actions when creating, reading, updating or deleting an object | Yes, using [Webhooks](/docs/reference/access-authn-authz/extensible-admission-controllers/#admission-webhooks). | Yes |
 | Scale Subresource | Allows systems like HorizontalPodAutoscaler and PodDisruptionBudget interact with your new resource | [Yes](/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/#scale-subresource)  | Yes |
 | Status Subresource | Allows fine-grained access control where user writes the spec section and the controller writes the status section. Allows incrementing object Generation on custom resource data mutation (requires separate spec and status sections in the resource) | [Yes](/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/#status-subresource) | Yes |
@@ -203,7 +203,7 @@ When you create a custom resource, either via a CRD or an AA, you get many featu
 | merge-patch | The new endpoints support PATCH with `Content-Type: application/merge-patch+json` |
 | HTTPS | The new endpoints uses HTTPS |
 | Built-in Authentication | Access to the extension uses the core API server (aggregation layer) for authentication |
-| Built-in Authorization | Access to the extension can reuse the authorization used by the core API server (e.g. RBAC) |
+| Built-in Authorization | Access to the extension can reuse the authorization used by the core API server (For example, RBAC) |
 | Finalizers | Block deletion of extension resources until external cleanup happens. |
 | Admission Webhooks | Set default values and validate extension resources during any create/update/delete operation. |
 | UI/CLI Display | Kubectl, dashboard can display extension resources. |
@@ -217,7 +217,7 @@ There are several points to be aware of before adding a custom resource to your
 
 ### Third party code and new points of failure
 
-While creating a CRD does not automatically add any new points of failure (e.g. by causing third party code to run on your API server), packages (e.g. Charts) or other installation bundles often include CRDs as well as a Deployment of third-party code that implements the business logic for a new custom resource.
+While creating a CRD does not automatically add any new points of failure (For example, by causing third party code to run on your API server), packages (For example, Charts) or other installation bundles often include CRDs as well as a Deployment of third-party code that implements the business logic for a new custom resource.
 
 Installing an Aggregated API server always involves running a new Deployment.