Merge pull request #40 from nesi/lbrick-patch-1

Update main create and mange identity page

Author: lbrick

docs/user-guides/create-and-manage-identity/index.md

@@ -12,7 +12,7 @@ vote_sum: 1
 
 `Application Credentials` help you to avoid the practice of embedding user account credentials in configuration files. Instead, the user creates an Application Credential that receives delegated access to a single project and has its own distinct secret. The user can also limit the delegated privileges to a single role in that project. This allows you to adopt the principle of least privilege, where the authenticated service only gains access to the one project and role that it needs to function, rather than all of them.
 
-This approach allows you to consume an API with revealing your user credentials, and lets applications authenticate to Keystone without requiring embedded user credentials.
+This approach allows you to consume an API without revealing your user credentials, and lets applications authenticate to Keystone without requiring embedded user credentials.
 
 Within FlexiHPC you are able to mange `Application Credentials` from the dashboard and/or the CLI.
 
@@ -21,4 +21,4 @@ Within FlexiHPC you are able to mange `Application Credentials` from the dashboa
 - [Creating and Managing Application Credentials via CLI](creating-and-managing-application-credentials-via-cli.md)
 
 !!! note
-    The Application Credential is dependent on the user account that created it, so it will terminate if that account is ever deleted, or loses access to the relevant role.
+    The Application Credential is dependent on the user account that created it, so it will terminate if that account is ever deleted, or loses access to the relevant role.