feat(storage): update

Author: SamyOubouaziz

pages/object-storage/how-to/host-healthcare-data.mdx

@@ -24,7 +24,7 @@ This documentation provides the following elements:
 
 - A Scaleway account logged into the [console](https://console.scaleway.com)
 - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
-- Signed an HDS contract with Scaleway for the garantees outlined in the [shared responsibility model](/object-storage/reference-content/storage-shared-responsibility-model/) to apply
+- Signed an HDS contract with Scaleway for the guarantees outlined in the [shared responsibility model](/object-storage/reference-content/storage-shared-responsibility-model/) to apply
 
 ## How to create a compliant bucket
 
@@ -54,13 +54,13 @@ Your bucket is now ready to store healthcare data. Before uploading objects, ref
 
 ## Prohibited actions on a compliant Bucket
 
-to host healthcare data, you must comply to the following requirements:
+to host healthcare data, you must comply with the following requirements:
 
 - You must not use the [Glacier](/object-storage/concepts/#storage-classes) storage class. Refer to the [Shared responsibility model](/object-storage/reference-content/storage-shared-responsibility-model/) for more information on this requirement.
 
 - You must not use [lifecycle rules](/object-storage/concepts/#lifecycle-configuration) in your compliant bucket.
 
-- If you use a [customer-side encryption mechanism](#customer-side-encryption), you must no delete the bucket encryption.
+- If you use a [customer-side encryption mechanism](#customer-side-encryption), you must not delete the bucket encryption.
 
 <Message type="important">
 Failure to comply with these requirements may lead to voiding compliance on the objects contained in the bucket.
@@ -72,27 +72,27 @@ Objects in a compliant bucket must be encrypted to make sure data is protected.
 
 ### Encryption with SSE-C
 
-Scaleway's SSE-C (**S**erver-**S**ide **E**ncryption with **C**ustomer-provided keys) mechanism garantees that objects uploaded to the bucket are properly encrypted.
+Scaleway's SSE-C (**S**erver-**S**ide **E**ncryption with **C**ustomer-provided keys) mechanism guarantees that objects uploaded to the bucket are properly encrypted.
 
-You can check that your objects are propery encrypted by performing a simple `HeadObject` operation on an encrypted object. Scaleway Object Storage will return a `400` error if SSE-C has been used to upload this object.
+You can check that your objects are properly encrypted by performing a simple `HeadObject` operation on an encrypted object. Scaleway Object Storage will return a `400` error if SSE-C has been used to upload this object.
 
 Refer to the [dedicated documentation](/object-storage/api-cli/enable-sse-c/) for comprehensive information on how to encrypt objects using SSE-C.
 
 ### Customer-side encryption
 
-Customer-side encryption ensures that sensitive data is protected before reaching Scaleway Object Storage, giving you control on the encryption mechanism, and keys managemnent. This method must be used in combination with [Scaleway's HDS-compliant deletion method](#deleting-objects-with-customer-side-encryption).
+Customer-side encryption ensures that sensitive data is protected before reaching Scaleway Object Storage, giving you control over the encryption mechanism, and keys management. This method must be used in combination with [Scaleway's HDS-compliant deletion method](#deleting-objects-with-customer-side-encryption).
 
 ## How to delete objects
 
-Objects must be deleted in a compliant way to make sure data can not be retrieved by any means immediately afterward. When using the HDS-compliant method (using the `PutBucketEncryption` action), Scaleway encrypts your uploaded objects with a dedicated key that will be instantly deleted upon receiving a deletion request for the targeted objects.
+Objects must be deleted in a compliant way to make sure data cannot be retrieved by any means immediately afterward. When using the HDS-compliant method (using the `PutBucketEncryption` action), Scaleway encrypts your uploaded objects with a dedicated key that will be instantly deleted upon receiving a deletion request for the targeted objects.
 
-This mechanism guarantees your objects can not be immediately retrieved, even if it takes additionnal time to process the delete of all the remaining chunks of your deleted objects.
+This mechanism guarantees your objects cannot be immediately retrieved, even if it takes additional time to process the delete of all the remaining chunks of your deleted objects.
 
 ### Deleting objects encrypted with SSE-C
 
-If you use Scaleway's SSE-C to encrypt your data, using [DeleteObject](/object-storage/api-cli/object-operations/#deleteobject) is sufficient to garantee that your object is deleted in compliance with the regulatory requirements. 
+If you use Scaleway's SSE-C to encrypt your data, using [DeleteObject](/object-storage/api-cli/object-operations/#deleteobject) is sufficient to guarantee that your object is deleted in compliance with the regulatory requirements. 
 
-### Deleting objects with customer-side encrpytion
+### Deleting objects with customer-side encryption
 
 If you do not use Scaleway's SSE-C to encrypt your data, you must use Scaleway's HDS-compliant method to delete objects. You must enable bucket encryption beforehand, using the `PutBucketEncryption` operation.