Some minor wording updates

source/integrate-with-integration-environment/authenticate-your-user.html.md.erb

@@ -58,7 +58,7 @@ If you need to authenticate your user and check their identity, you should send
 By using 2 separate requests: 
 
 * more users are likely to create their account successfully
-* you can track which users could not verify their identity
+* you can track which users could not prove their identity
 * you can support your users better when returning from an in-person identity check because you’ll have authenticated them previously
 * you simplify the migration of existing users to GOV.UK One Login
 

source/integrate-with-integration-environment/index.html.md.erb

@@ -9,7 +9,7 @@ review_in: 6 months
 
 Before you can use GOV.UK One Login, you need to build a proof of concept client and explore the end-to-end journey in our integration environment. This will help you understand how to integrate with GOV.UK One Login, and where it will fit within your service.
 
-If your service requires identity assurance, you must authenticate your users first. 
+If your service requires identity proving, you must authenticate your users first. 
 
 1. [Authenticate your user][integrate.authenticate].
 1. [Prove your user's identity][integrate.identity-proving].

source/integrate-with-integration-environment/prove-users-identity.html.md.erb

@@ -7,15 +7,15 @@ review_in: 6 months
 
 # Prove your user's identity
 
-You must have authenticated your users before you can verify their identity.
+You must have authenticated your users before you can prove their identity.
 
-If you [requested identity assurance][integrate.choose-level-of-confidence], when you [retrieve user information with `/userinfo`][integrate.retrieve-user-info], you’ll receive a response containing additional claims (user attributes). You may receive different claims, depending on how your user proved their identity.
+If you [requested identity proving][integrate.choose-level-of-confidence], when you [retrieve user information with `/userinfo`][integrate.retrieve-user-info], you’ll receive a response containing additional claims (user attributes). You may receive different claims, depending on how your user proved their identity.
 
 Your service’s needs will determine how you process the other claims that GOV.UK One Login provides about your user. You’ll probably need to match against information held by your service or organisations you work with.
 
 Most claims are represented by JSON objects. The [core identity claim](#understand-your-user-s-core-identity-claim) is a JSON web token (JWT) protected by an electronic signature for additional security.
 
-You’ll receive a response from `userinfo` that will look similar to this example:
+You’ll receive a response from `/userinfo` that will look similar to this example:
 
 ```
 HTTP/1.1 200 OK