Review for grammar, readability

Author: dg-concordium

source/mainnet/net/guides/wallet-sdk/wallet-sdk-account-transaction.rst

@@ -1,11 +1,11 @@
 .. _wallet-sdk-account-transaction:
 
-=============================================
-Submitting a transaction to a Concordium node
-=============================================
+=========================================
+Submit a transaction to a Concordium node
+=========================================
 
-The following sections document the requirements for creating an account transaction, signing it and
-finally sending it to a Concordium node.
+The following sections document the requirements for creating an account transaction, signing it, and
+sending it to a Concordium node.
 
 * `Construct an account transaction`_
 * `Sign an account transaction`_
@@ -15,8 +15,7 @@ finally sending it to a Concordium node.
 Construct an account transaction
 ++++++++++++++++++++++++++++++++
 
-For the sake of this example we will be constructing a simple transfer, which is an account transaction that moves an amount of CCD from one account to another. For other transaction types the steps are similar,
-but the exact fields that must be provided for the payload will be different.
+This example constructs a simple transfer, which is an account transaction that moves an amount of CCD from one account to another. For other transaction types, the steps are similar, but the exact fields that must be provided for the payload will be different.
 
 .. tabs::
 
@@ -90,9 +89,9 @@ but the exact fields that must be provided for the payload will be different.
 Sign an account transaction
 +++++++++++++++++++++++++++
 
-Having constructed an account transaction the next step is to sign it. It is important that the key used to sign an account transaction matches the sender address provided in the account transaction header. We note here that Concordium as a whole supports multi-signature transactions, but for the purpose of this example we will demonstrate how to do it for an account with a single credential that has a single key.
+Having constructed an account transaction, the next step is to sign it. It is important that the key used to sign an account transaction matches the sender address provided in the account transaction header. Note that Concordium as a whole supports multi-signature transactions, but for the purpose of this example it will demonstrate how to do it for an account with a single credential that has a single key.
 
-Please note that when the transaction has been signed anyone with the signature and the transaction will be able to send it to a Concordium node. Therefore it is very important that a wallet requests user approval before utilizing their signing keys.
+Note that when the transaction has been signed anyone with the signature and the transaction will be able to send it to a Concordium node. Therefore it is very important that a wallet requests user approval before utilizing their signing keys.
 
 .. tabs::
 

source/mainnet/net/guides/wallet-sdk/wallet-sdk-credential-deployment.rst

@@ -1,11 +1,10 @@
 .. _wallet-sdk-credential-deployment:
 
-===================
-Creating an account
-===================
+=================
+Create an account
+=================
 
-Having created an identity the next step is to create an account. On Concordium an account is an entity that can hold multiple credentials, but for the sake of keeping the example simple, the following
-guide will describe how to create an account with a single credential.
+Having created an identity, the next step is to create an account. On Concordium, an account is an entity that can hold multiple credentials, but for the sake of keeping the example simple, the following guide will describe how to create an account with a single credential.
 
 * `Create a credential deployment transaction`_
 * `Sign a credential deployment transaction`_
@@ -15,8 +14,7 @@ guide will describe how to create an account with a single credential.
 Create a credential deployment transaction
 ++++++++++++++++++++++++++++++++++++++++++
 
-The following example demonstrates how a credential deployment transaction is created. Note that you must have saved the identity object and the identity provider that was used to create that identity, as they are required
-input for this transaction type.
+The following example demonstrates how a credential deployment transaction is created. Note that you must have saved the identity object and the identity provider that was used to create that identity, as they are required input for this transaction type.
 
 .. tabs::
 
@@ -158,8 +156,8 @@ Having created and signed the credential deployment transaction, the final step
 utility function that does this by simply providing it the credential deployment transaction and the signature on the transaction. The result
 of the call is a transaction hash that can then be used to monitor the status of the transaction.
 
-If successful, the credential will have been deployed, and it is now possible to start creating account transactions. Go to
-:ref:`wallet-sdk-account-transaction` for a guide on how that is done.
+If successful, the credential will be deployed, and it is now possible to start creating account transactions. Go to
+:ref:`wallet-sdk-account-transaction` for a guide about creating account transactions.
 
 .. tabs::
 

source/mainnet/net/guides/wallet-sdk/wallet-sdk-identity-creation.rst

@@ -1,21 +1,21 @@
 .. _wallet-sdk-identity-creation:
 
-====================
-Creating an identity
-====================
+==================
+Create an identity
+==================
 
-To create an account on the Concordium blockchain, one must first acquire an identity. Therefore, as an initial step, a user of a wallet will always have to create an identity before being able to send account transactions.
+To create an account on the Concordium blockchain, a user must first acquire an identity. Therefore, as an initial step, a wallet user will always have to create an identity before being able to send account transactions.
 
 An identity is acquired by generating an identity request and sending it to an identity provider. The user will then be taken through the identity verification
 process that is specific for that chosen identity provider. This happens outside of the wallet application.
 
-* `Creating an identity request`_
-* `Sending an identity request`_
-* `Retrieving the identity after creation`_
+* `Create an identity request`_
+* `Send an identity request`_
+* `Retrieve the identity after creation`_
 
-++++++++++++++++++++++++++++
-Creating an identity request
-++++++++++++++++++++++++++++
+++++++++++++++++++++++++++
+Create an identity request
+++++++++++++++++++++++++++
 
 The first step is to create the actual identity request. To do this, you need the list of identity providers. Refer to :ref:`Identity Provider List` to understand how to retrieve it.
 
@@ -91,16 +91,13 @@ The first step is to create the actual identity request. To do this, you need th
 
         The Swift SDK for iOS is still in development.
 
-+++++++++++++++++++++++++++
-Sending an identity request
-+++++++++++++++++++++++++++
+++++++++++++++++++++++++
+Send an identity request
+++++++++++++++++++++++++
 
 Once the identity request has been created, the next step is to send it to the corresponding identity provider. There are multiple ways to accomplish this, and it will depend on the technologies you choose. Below is an example of how it can be done.
 
-A part of the request is a `redirectUri`, which tells the identity provider where to redirect the user when the identity verification flow has been completed. A wallet application has to
-choose this in such a way that the user is sent back into the wallet application, where the
-actual identity object can then be retrieved from the information provided in the hash property
-of the redirect URL.
+A part of the request is a `redirectUri`, which tells the identity provider where to redirect the user when the identity verification flow has been completed. A wallet application has to choose this in such a way that the user is sent back into the wallet application, where the actual identity object can then be retrieved from the information provided in the hash property of the redirect URL.
 
 .. tabs::
 
@@ -163,13 +160,11 @@ of the redirect URL.
 
         The Swift SDK for iOS is still in development.
 
-++++++++++++++++++++++++++++++++++++++
-Retrieving the identity after creation
-++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++
+Retrieve the identity after creation
+++++++++++++++++++++++++++++++++++++
 
-Upon completing identity verification at the identity provider, the identity provider does a
-redirect of the user back to the `redirectUri` that was provided when sending the identity request to the identity provider. The hash property of the URL that the identity provider
-redirects the user to contains the URL where the identity object can be retrieved from, in the format `redirectUri#code_uri=`, where the URL will be after the equals sign.
+Upon completing identity verification with the identity provider, the identity provider does a redirect of the user back to the `redirectUri` that was provided when sending the identity request to the identity provider. The hash property of the URL that the identity provider redirects the user to contains the URL where the identity object can be retrieved from in the format `redirectUri#code_uri=`, where the URL will be after the equals sign.
 
 .. tabs::
 

source/mainnet/net/guides/wallet-sdk/wallet-sdk-identity-provider.rst

@@ -1,8 +1,8 @@
 .. _wallet-sdk-identity-provider:
 
-======================================
-Getting the list of identity providers
-======================================
+==================================
+Get the list of identity providers
+==================================
 
 The list of identity providers can be retrieved from a Concordium node; however, the provided list lacks the necessary metadata for creating or recovering an identity from an identity provider. Therefore, Concordium hosts a service called the wallet-proxy that serves this information to wallets.
 

source/mainnet/net/guides/wallet-sdk/wallet-sdk-identity-recovery.rst

@@ -1,21 +1,21 @@
 .. _wallet-sdk-identity-recovery:
 
-======================
-Recovering an identity
-======================
+===================
+Recover an identity
+===================
 
 The following sections demonstrate the process of creating a request to recover an identity from an identity provider. While accounts are stored on the Concordium blockchain, identities are stored by the selected identity provider during the creation process, and recovery is initiated by sending a request to that specific identity provider.
 
-* `Generating an identity recovery request`_
-* `Sending an identity recovery request`_
+* `Generate an identity recovery request`_
+* `Send an identity recovery request`_
 
-+++++++++++++++++++++++++++++++++++++++
-Generating an identity recovery request
-+++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++
+Generate an identity recovery request
++++++++++++++++++++++++++++++++++++++
 
 The following example demonstrates the process of generating an identity recovery request. Part of the input to the request is a secret value derived from the seed phrase, and this value should be kept secret in a similar manner as the seed phrase and account signing keys.
 
-In the example below, functionality for retrieving the list of identity providers is present. To see an example of how to implement this function, please check out :ref:`Identity Provider List`.
+In the example below, functionality for retrieving the list of identity providers is present. To see an example of how to implement this function, see :ref:`Identity Provider List`.
 
 .. tabs::
 
@@ -67,9 +67,9 @@ In the example below, functionality for retrieving the list of identity provider
 
         The Swift SDK for iOS is still in development.
 
-++++++++++++++++++++++++++++++++++++
-Sending an identity recovery request
-++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++
+Send an identity recovery request
++++++++++++++++++++++++++++++++++
 
 The next step is to send the generated identity recovery request to the associated identity provider. If successful, the identity provider will return a redirect to the location from which the identity can be fetched.
 

source/mainnet/net/guides/wallet-sdk/wallet-sdk.rst

@@ -8,7 +8,7 @@ This integration guide is directed towards developers who want to implement thei
 This typically means either a mobile wallet (iOS or Android), or a solution building on TypeScript or JavaScript.
 
 The SDK provides the necessary functions to derive the correct Concordium keys from a secret recovery phrase, to
-generate the Concordium specific requests to create and recover identities, to create and deploy a credential and
+generate the Concordium specific requests to create and recover identities, to create and deploy a credential, and
 to create and send transactions to a Concordium node.
 
 Below, you can find a link to the SDK package for your chosen technology, and an example wallet that demonstrates its usage.