EN proof

Author: tcpdumpfbacke

Diff for: pages/manage_and_operate/iam/identities-management/guide.en-gb.md

@@ -10,7 +10,7 @@ The purpose of this guide is to present the different types of identities that c
 
 ## Requirements
 
-- An [OVHcloud customer account](/pages/account_and_service_management/account_information/ovhcloud-account-creation).
+- An [OVHcloud customer account](/pages/account_and_service_management/account_information/ovhcloud-account-creation)
 
 ## Instructions
 
@@ -34,13 +34,13 @@ Local users are identities associated with your OVHcloud account. These accounts
 
 The configuration of local users is detailed in the [dedicated documentation](/pages/account_and_service_management/account_information/ovhcloud-users-management).
 
-You can also use them to log in to the OVHcloud APIs by [generating a token associated with the user](/pages/manage_and_operate/api/first-steps). The rights of this token can be limited to a specific scope in addition to IAM policies.
+You can also use them to log in to the OVHcloud API by [generating a token associated with the user](/pages/manage_and_operate/api/first-steps). The rights of this token can be limited to a specific scope in addition to IAM policies.
 
 In order for an application based on a token linked to a local user to use an OVHcloud API, it is therefore necessary for the token to integrate it within its scope **AND** that the user who created the token has rights on this API.
 
 Local users can also be referred to as *sub-users* in the documentation.
 
-We recommend to use local users as soon as more than one person should connect to your OVHcloud account in order to assure tracability of the actions
+We recommend to use local users as soon as more than one person connects to your OVHcloud account in order to assure traceability of the actions.
 
 ### Service accounts
 
@@ -56,7 +56,7 @@ These are user accounts from an [identity federation](/products/manage-operate-u
 
 Federated users are represented by user groups in rights management.
 
-We recommand to use identity federation as soon as the number of person that should connect to your OVHcloud account became large enough, or if you want to centralise your access to a third party directory used for other services than OVHcloud
+We recommend to use identity federation as soon as the number of persons that connect to your OVHcloud account becomes large enough, or if you want to centralize your access to a third-party directory used for other services than OVHcloud.
 
 ### User groups
 
@@ -65,11 +65,11 @@ Configuring user groups is covered in the [local users management documentation]
 
 ### Users of OVHcloud products
 
-Some products offer by OVHcloud can also propose their own users, such as Openstack, VMware vSphere or Object Storage.
-Those users are independant from the OVHcloud account and are managed directly through the products concerned.
+Some products offered by OVHcloud can also propose their own users, such as OpenStack, VMware vSphere or Object Storage.  
+Those users are independent from the OVHcloud account and are managed directly through the products concerned.
 
-For the products allowing to choose to use an OVHcloud identity (local user, service account, federated user) or a specific user, if you would like to maintain the reversibility of it and limit the dependency with OVHcloud we recommand to use those specific users.
-On the opposite, if you want to have a centralise management accross all your products we suggest to use OVHcloud identities.
+For the products allowing to choose to use an OVHcloud identity (local user, service account, federated user) or a specific user, if you would like to maintain the reversibility of it and limit the dependency on OVHcloud, we recommend to use those specific users.  
+On the other hand, if you want to have centralized management across all your products, we suggest to use OVHcloud identities.
 
 ## Go further