diff --git a/deployable-architecture-responsibilities.md b/deployable-architecture-responsibilities.md index 4e5943c..6223d56 100644 --- a/deployable-architecture-responsibilities.md +++ b/deployable-architecture-responsibilities.md @@ -101,8 +101,8 @@ Disaster recovery includes tasks such as providing dependencies on disaster reco | Task | {{site.data.keyword.IBM_notm}} Responsibilities | Your Responsibilities | |----------|-----------------------|--------| -| Meet disaster recovery objectives| {{site.data.keyword.IBM_notm}} follows best practices for disaster recovery. All {{site.data.keyword.IBM_notm}} applications automatically recover and restart after any disaster event. For more information about disaster recovery, see the [{{site.data.keyword.IBM_notm}} Disaster Recovery Plan](/docs/overview?topic=overview-zero-downtime#disaster-recovery). | Customers can help meet disaster recovery objectives by deploying their project in a development or test environment before they deploy to production. \n\nThe customer does not have to take other actions to prepare for an event of a catastrophic failure in a region. | -| Meet high availability objectives| {{site.data.keyword.cloud_notm}} is available globally and load balanced from a single URL. It is highly available and continues to run even if your resources are unavailable. For more information about high availability, see the [{{site.data.keyword.IBM_notm}} service level objectives](/docs/overview?topic=overview-slo) and the [sample application architecture](/docs/overview?topic=overview-bcdr-app-recovery). | N/A | +| Meet disaster recovery objectives| {{site.data.keyword.IBM_notm}} follows best practices for disaster recovery for the IBM Cloud Platform and Services. For more information about disaster recovery, see the [{{site.data.keyword.IBM_notm}} Disaster Recovery Plan](/docs/overview?topic=overview-zero-downtime#disaster-recovery). | Customers can help meet disaster recovery objectives when using deployable architectures by [understanding their responsibilities](/docs/overview?topic=overview-understanding-dr) and maintaining a Disaster Recovery Plan for Services and Software deployed using deployable architectures as well as customer owned data stored within those Services or Software | +| Meet high availability objectives| {{site.data.keyword.cloud_notm}} is available globally and load balanced from a single URL. It is highly available and continues to run even if your resources are unavailable. For more information about high availability, see the [{{site.data.keyword.IBM_notm}} service level objectives](/docs/overview?topic=overview-slo) and the [sample application architecture](/docs/overview?topic=overview-bcdr-app-recovery). | Deployable architectures represent best practice deployment patterns. It is the customer responsibility to [understand high availability considerations](/docs/overview?topic=overview-ha-considerations) when selecting and configuring deployable architectures. | {: row-headers} {: caption="Table 5. Responsibilities for disaster recovery" caption-side="bottom"} {: summary="The first column describes the task that a customer or IBM might be responsibility for. The second column describes {{site.data.keyword.IBM_notm}} responsibilities for that task. The third column describes your responsibilities as the customer for that task."}