From 972c905b23313b288325bcc3cac83e05cb47141b Mon Sep 17 00:00:00 2001 From: Shilla Saebi Date: Tue, 28 Jan 2014 12:20:19 -0500 Subject: [PATCH] slight change on ch064_certifications-compliance-statements MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit “Does” is singular, revised - "do" changed to does Change-Id: If51652336e44bcd6e9ee5e9b1755c023ba0465cb --- .../ch064_certifications-compliance-statements.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/security-guide/ch064_certifications-compliance-statements.xml b/doc/security-guide/ch064_certifications-compliance-statements.xml index b6df2e934b..c76dc272c0 100644 --- a/doc/security-guide/ch064_certifications-compliance-statements.xml +++ b/doc/security-guide/ch064_certifications-compliance-statements.xml @@ -151,7 +151,7 @@ HIPAA is not a certification, rather a guide for protecting healthcare data.  Similar to the PCI-DSS, the most important issues with both PCI and HIPPA is that a breach of credit card - information, and health data, do not occur. In the instance of a + information, and health data, does not occur. In the instance of a breach the cloud provider will be scrutinized for compliance with PCI and HIPPA controls. If proven compliant, the provider can be expected to immediately implement remedial controls,