Merge pull request #1760 from coligo/fmo-upd-31Jan22-a

cfsdocs · cfsdocs · commit 1d6b6fa6f906 · 2022-01-31T21:04:25.000Z
diff --git a/about.md b/about.md
@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2022
-lastupdated: "2022-01-28"
+lastupdated: "2022-01-31"
 
 keywords: benefits, terminology, developers, capabilities, code engine
 
@@ -31,7 +31,7 @@ Review the capabilities that {{site.data.keyword.codeengineshort}} provides to r
 | Private workloads | Store your source code in private repositories and push your images to private registries and {{site.data.keyword.codeengineshort}} can access them. |
 | Fully integrated | {{site.data.keyword.codeengineshort}} is fully integrated into IBM Cloud so that you can take advantage of the full catalog of IBM Cloud services. |
 | Event-driven workloads | Extend the functionality of your applications with messages (events) from event producers. Your application can then react to those events and perform actions based on them. |
-| Auto-scales - even to zero | {{site.data.keyword.codeengineshort}} automatically scales your workloads up and down, and even down to zero when no requests are active. You pay for only the resources that you consume. |
+| Autoscales - even to zero | {{site.data.keyword.codeengineshort}} automatically scales your workloads up and down, and even down to zero when no requests are active. You pay for only the resources that you consume. |
 | Control access | Assign platform and services access permissions to your projects in IBM Cloud Identity and Access Management to control who can provision and manage resources in your IBM Cloud account. |
 | Based on open source | {{site.data.keyword.codeengineshort}} is built on a set of open source technologies such as Kubernetes, Knative, Istio, and Tekton, keeping your apps and jobs portable. |
 {: caption="Table 1. {{site.data.keyword.codeengineshort}} benefits" caption-side="bottom"}
diff --git a/add-registry.md b/add-registry.md
@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2022
-lastupdated: "2022-01-28"
+lastupdated: "2022-01-31"
 
 keywords: registries, container registry, image registry, apikey, API key, access token, images, registry access, service id
 
@@ -42,7 +42,7 @@ Public registries, such as public Docker Hub, can be used to get started with Do
 ## Setting up authorities for image registries
 {: #authorities-registry}
 
-if your registry is public, you do not have to set up authorities in order to pull images. Note that pulling images from a public registry while you are getting started with {{site.data.keyword.codeengineshort}} is acceptable, use a private registry when it comes to your enterprise workloads.
+If your registry is public, you do not have to set up authorities to pull images. Note that pulling images from a public registry while you are getting started with {{site.data.keyword.codeengineshort}} is acceptable. Use a private registry when it comes to your enterprise workloads.
 
 **What authorities do I need?**
 
@@ -52,7 +52,7 @@ When you deploy apps or run jobs from the console, {{site.data.keyword.codeengin
 |--------|-----------|---------------------|
 | Pull images | `Read` access | When you deploy an image as an application or job, you must pull the image from a registry. To pull images, you need `read` access. Note that if the repository is public, you already have `read` access to the images. |
 | Push images | `Read` and `write` access | When you build source code, you must push the image to a registry. To push images, you need `write` access to {{site.data.keyword.registryfull_notm}}. You cannot push images to a registry other than {{site.data.keyword.registryfull_notm}}. |
-| Create a namespace | `Read`, `write`, and `Manager` access | To create a namespace in {{site.data.keyword.registrylong_notm}}, you must have `manager` access. In order to pull and push images, you must have `read` and `write` access. |
+| Create a namespace | `Read`, `write`, and `Manager` access | To create a namespace in {{site.data.keyword.registrylong_notm}}, you must have `manager` access. To pull and push images, you must have `read` and `write` access. |
 {: caption="Access authorities for image registry" caption-side="top"}
 
 **Can I use a service ID?**
@@ -124,7 +124,7 @@ Now that you created your API key, [save it as registry access](#add-registry-ac
 ## Accessing images in a shared account
 {: #images-shared-account}
 
-In order to access images from {{site.data.keyword.registryfull_notm}} in a shared account, you must be assigned the [proper authority](#authorities-registry).
+To access images from {{site.data.keyword.registryfull_notm}} in a shared account, you must be assigned the [proper authority](#authorities-registry).
 
 If you are planning to deploy apps and run jobs from the shared account, {{site.data.keyword.codeengineshort}} can pull or push images for you when you deploy your application or create your job.
 
@@ -210,7 +210,7 @@ When you create a service ID, you can restrict access to a regional {{site.data.
 ### Authorizing access to {{site.data.keyword.registryshort}} with service ID from the console
 {: #authorize-console-service-id}
 
-In order to pull or push images from or to {{site.data.keyword.registryfull_notm}}, you must create a service ID, create an access policy for the service ID, and then create an API key to store the credentials.
+To pull or push images from or to {{site.data.keyword.registryfull_notm}}, you must create a service ID, create an access policy for the service ID, and then create an API key to store the credentials.
 
 #### Step 1 Create the service ID and authorize it to the {{site.data.keyword.registryfull_notm}} service
 {: #create-service-id}
@@ -252,12 +252,12 @@ Now that our service ID is created and is granting access to {{site.data.keyword
     5. Click **Add** and then **Assign**.
 
 
-Now that you have your access policies in place for your service ID and your API key created, you can [add access to {{site.data.keyword.codeengineshort}}](#add-registry-access-ce) in order to pull images from your container registry.
+Now that you have your access policies in place for your service ID and your API key created, you can [add access to {{site.data.keyword.codeengineshort}}](#add-registry-access-ce) to pull images from your container registry.
 
 ### Authorizing access to {{site.data.keyword.registryshort}} with the CLI
 {: #authorize-cr-cli}
 
-In order to pull images from {{site.data.keyword.registryfull_notm}} in a different account, you must create a service ID, create access policies for the service ID, and then create an API key to store your credentials.
+To pull images from {{site.data.keyword.registryfull_notm}} in a different account, you must create a service ID, create access policies for the service ID, and then create an API key to store your credentials.
 {: shortdesc}
 
 1. Create an {{site.data.keyword.cloud_notm}} IAM service ID for your project that is used for the IAM policies and API key credentials in the image pull secret with the **`iam service-id-create`** command. Be sure to give the service ID a description that helps you retrieve the service ID later, such as including the project name. For a complete listing of the **`iam service-id-create`** command and its options, see the [**`ibmcloud iam service-id-create`**](/docs/account?topic=cli-ibmcloud_commands_iam#ibmcloud_iam_service_id_create) command.
@@ -334,4 +334,4 @@ In order to pull images from {{site.data.keyword.registryfull_notm}} in a differ
     You won’t be able to see this API key again, so be sure to record it in a safe place.
     {: important}
 
-    Now that you have your access policies in place for your service ID and your API key created, you can [add access to {{site.data.keyword.codeengineshort}}](#add-registry-access-ce) in order to pull images from your container registry.
+    Now that you have your access policies in place for your service ID and your API key created, you can [add access to {{site.data.keyword.codeengineshort}}](#add-registry-access-ce) to pull images from your container registry.
diff --git a/cli-changelog.md b/cli-changelog.md
@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2022
-lastupdated: "2022-01-28"
+lastupdated: "2022-01-31"
 
 keywords: cli change log for code engine, cli version for code engine, change log for cli in code engine, cli history for code engine, change log, cli version history
 
@@ -53,7 +53,7 @@ Find a summary of changes for each version of {{site.data.keyword.codeenginefull
 | 1.3.0 | 21 April 2021 | - Added `--wait`, `--no-wait`, and `--wait-timeout` options to the **`project delete`** command. \n - Added support for `CloudEvent` extensions on **`subscription COS`** and **`subscription ping`** commands. This support adds the `--extensions` option to the **`subscription COS create`**, **`subscription COS update`**, **`subscription ping create`**, and **`subscription ping update`** commands. Also adds the `--extensions-rm` option to the **`subscription COS update`** and **`subscription ping update`** commands to remove `CloudEvent` extensions. \n - Updated the project status on the output for the **`project get`** and the **`project list`** commands. The status of `provisioning` is changed to `creating`, and the status of `pending reclamation` is changed to `soft deleted`. \n - Fixed various minor bugs.|
 | 1.2.0 | 13 April 2021 | -  **New! Subscription support for jobs as a beta function.** Added support for jobs as event destinations. Use the `--destination-type` option with the **`subscription ping create`**, **`subscription ping update`**, **`subscription cos create`**, and **`subscription cos update`** commands to specify the event destination. Valid values for this option are `app` and `job`. \n - Updated the **`project get`** command to display project quota information.|
 | 1.1.0 | 07 April 2021 | -  Increased the polling frequency when waiting for build runs and job runs to complete.  \n - Updated the **`project delete`** command such that if a project was previously deleted without specifying the `--hard` option, a subsequent **`project delete`** command must use the `--hard` option.  \n - Updated the **`project select`** command such that a project must be in `active` status before it can be selected. \n - Updated the output for the **`project list`** and **`project get`** commands to display projects that are in `pending_reclamation` status.|
-| 1.0.0 | 30 March 2021 | This is the generally available release of {{site.data.keyword.codeengineshort}} CLI.- **Important:** Introduced a breaking change to {{site.data.keyword.codeengineshort}} service binding functionality. Service bindings that were created with releases of the CLI earlier than release 1.0.0 will no longer work after updating to the CLI 1.0.0 release. Unbind pre-existing service bindings before updating to CLI 1.0.0. \n - Updated service bindings to use a new naming convention. Binding names are now auto-generated to ensure uniqueness. \n - Updated the **`app unbind`** and **`job unbind`** commands to accept the `--binding` option. The `--binding` option replaces the `--service-instance` option.  \n - Renamed the service binding `VCAP_SERVICES` environment variable, which is injected into running containers, to `CE_SERVICES`. \n - Updated application and job service bindings to support multiple service bindings to the same service instance. \n -  Updated support for service bindings such that service bindings that are created without existing service credentials always generate a new, unique service credential.  \n - Added more information to output for bad request errors encountered by the CLI.|
+| 1.0.0 | 30 March 2021 | This is the generally available release of {{site.data.keyword.codeengineshort}} CLI.- **Important:** Introduced a breaking change to {{site.data.keyword.codeengineshort}} service binding functionality. Service bindings that were created with releases of the CLI earlier than release 1.0.0 will no longer work after updating to the CLI 1.0.0 release. Unbind pre-existing service bindings before updating to CLI 1.0.0. \n - Updated service bindings to use a new naming convention. Binding names are now autogenerated to ensure uniqueness. \n - Updated the **`app unbind`** and **`job unbind`** commands to accept the `--binding` option. The `--binding` option replaces the `--service-instance` option.  \n - Renamed the service binding `VCAP_SERVICES` environment variable, which is injected into running containers, to `CE_SERVICES`. \n - Updated application and job service bindings to support multiple service bindings to the same service instance. \n -  Updated support for service bindings such that service bindings that are created without existing service credentials always generate a new, unique service credential.  \n - Added more information to output for bad request errors encountered by the CLI.|
 | 0.6.3 | 26 March 2021 | - Updated translations for the CLI.|
 {: caption="Changes in the IBM Cloud {{site.data.keyword.codeengineshort}} CLI" caption-side="top"} 
 
diff --git a/ha-dr.md b/ha-dr.md
@@ -2,7 +2,7 @@
 
 copyright:
   years: 2022
-lastupdated: "2022-01-28"
+lastupdated: "2022-01-31"
 
 keywords: HA for Code Engine, DR for Code Engine, high availability for Code Engine, disaster recovery for Code Engine, failover for Code Engine, backing up code engine, availability of code engine, code engine regions, backing up your Code Engine instance
 
@@ -27,7 +27,7 @@ The following table lists the high-availability (HA) status for the regions (loc
 
 | Geography | Region | High availability |
 |-------|-------|-------|
-| Asia Pactific | Australia (`au-syd`) | MZR |
+| Asia Pacific | Australia (`au-syd`) | MZR |
 | Asia Pacific | Osaka (`jp-osa`) | MZR |
 | Asia Pacific | Tokyo (`jp-tok`) | MZR |
 | Europe | Frankfurt (`eu-de`) | MZR | 
@@ -68,6 +68,6 @@ In a major regional disaster, such as an earthquake, flood, or tornado, an entir
 | `us-south` | `US` |
 {: caption="Table 2. Cross-regional endpoints" caption-side="top"}
 
-In order to avoid impacts on your workloads, such as duplication of jobs or deploying unwanted application instances, {{site.data.keyword.codeengineshort}} does not restore your workloads directly. Instead, restoring your workloads is you (the customer's) responsibility. For more information, see [Understanding your responsibilities when using {{site.data.keyword.codeengineshort}}](/docs/codeengine?topic=codeengine-responsibilities-ce).
+To avoid impacts on your workloads, such as duplication of jobs or deploying unwanted application instances, {{site.data.keyword.codeengineshort}} does not restore your workloads directly. Instead, restoring your workloads is you (the customer's) responsibility. For more information, see [Understanding your responsibilities when using {{site.data.keyword.codeengineshort}}](/docs/codeengine?topic=codeengine-responsibilities-ce).
 
 
diff --git a/troubleshoot-build.md b/troubleshoot-build.md
@@ -2,7 +2,7 @@
 
 copyright:
   years: 2020, 2022
-lastupdated: "2022-01-28"
+lastupdated: "2022-01-31"
 
 keywords: troubleshooting for code engine, troubleshooting builds in code engine, tips for builds in code engine, resolution of builds in code engine, builds
 
@@ -33,7 +33,7 @@ When your build isn't behaving as expected, looking at logs and system events ca
 
 The maximum number of build configurations that you can have per project is 100. You are limited to a total of 100 build runs per project before you need to remove or clean up old ones.
 
-For more information about limits for builds including memory and cpu, see [Limits and quotas for {{site.data.keyword.codeengineshort}}](/docs/codeengine?topic=codeengine-limits).
+For more information about limits for builds including memory and CPU, see [Limits and quotas for {{site.data.keyword.codeengineshort}}](/docs/codeengine?topic=codeengine-limits).
 
 ## Getting logs for my builds
 {: #ts-build-gettinglogs}
