fixes

topics/clients/client-oidc.adoc

@@ -76,13 +76,13 @@ _direct access only_::
 
 *Root URL*
 
-     If {{book.project.name}} uses any configured relative URLs, this value is prepended to them.
+If {{book.project.name}} uses any configured relative URLs, this value is prepended to them.
 
 *Valid Redirect URIs*
 
 This is a required field.  Enter in a URL pattern and click the + sign to add.  Click the - sign next to URLs you want to remove.
 Remember that you still have to click the `Save` button!
-Only wildcards, * ,are allowed at the end of of a URI, i.e. http://host.com/*
+Wildcards (*) are only allowed at the end of of a URI, i.e. http://host.com/*
 
 You should take extra precautions when registering valid redirect URI patterns. If you make
 them too general you are vulnerable to attacks.  See <<fake/../../threat/redirect.adoc#_unspecific-redirect-uris, Threat Model Mitigation>> chapter

topics/clients/client-saml.adoc

@@ -99,7 +99,7 @@ Root URL::
 Valid Redirect URIs::
   This is an optional field.  Enter in a URL pattern and click the + sign to add.  Click the - sign next to URLs you want to remove.
   Remember that you still have to click the `Save` button!
-  Only wildcards, * ,are allowed at the end of of a URI, i.e. http://host.com/*.  This field is used when the exact SAML
+  Wildcards (*) are only allowed at the end of of a URI, i.e. http://host.com/*.  This field is used when the exact SAML
   endpoints are not registered and {{book.project.name}} is pull the Assertion Consumer URL from the request.
 
 Base URL::

topics/identity-broker/social-login.adoc

@@ -4,5 +4,5 @@
 For Internet facing applications, it is quite burdensome for users to have to register at your site to obtain access.
 It requires them to remember yet another username and password combination.  Social identity providers allow you to delegate
 authentication to a semi-trusted and respected entity where the user probably already has an account.
-{{book.project.name}} provides built-in support for the most common social networks out there, such as Google, Facebook, Twitter, Github, LinkedId, Microsoft and StackOverflow.
+{{book.project.name}} provides built-in support for the most common social networks out there, such as Google, Facebook, Twitter, Github, LinkedIn, Microsoft and StackOverflow.
 

topics/identity-broker/social/facebook.adoc

@@ -34,7 +34,7 @@ for the application.  Click the `Settings` left menu item.
 .Create a New App ID
 image:../../../images/facebook-app-settings.png[]
 
-Click on the `+ Add Platform` button at the end of this page and select the `Website` icon.  Cut and past the `Redirect URI` from the
+Click on the `+ Add Platform` button at the end of this page and select the `Website` icon.  Copy and paste the `Redirect URI` from the
 {{book.project.name}} `Add identity provider` page into the `Site URL` of the Facebook `Website` settings block.
 
 .Specify Website

topics/identity-broker/social/google.adoc

@@ -38,7 +38,7 @@ and click the `Google+ API` link.
 image:../../../images/google-api-list.png[]
 
 Click the `Enable` button on this page.  You will get a message that you must create the credentials of your project.
-So click the `Go to Credentials` button
+So click the `Go to Credentials` button.
 
 .Go To Credentials
 image:../../../images/google-go-to-credentials.png[]
@@ -59,7 +59,7 @@ Select `Web server` and `User data` and click the `What credentials do I need?`
 image:../../../images/google-create-oauth-id.png[]
 
 Next you'll need to create an OAuth 2.0 client ID.  Specify the name you want for your client.  You'll also need to
-cut and paste the `Redirect URI` from the {{book.project.name}} `Add Identity Provider` page into the
+copy and paste the `Redirect URI` from the {{book.project.name}} `Add Identity Provider` page into the
 `Authorized redirect URIs` field.  After you do this, click the `Create client ID` button.
 
 When users log into Google from {{book.project.name}} they will see a consent screen from Google which will ask the user
@@ -78,5 +78,5 @@ Go back to {{book.project.name}} and specify those items.
 
 One config option to note on the `Add identity provider` page for Google is the `Default Scopes` field.
 This field allows you to manually specify the scopes that users must authorize when authenticating with this provider.
-For a complete list of scopes, please take a look at link:https://developers.google.com/oauthplayground/. By default, {{book.project.name}}
+For a complete list of scopes, please take a look at https://developers.google.com/oauthplayground/. By default, {{book.project.name}}
 uses the following scopes: `openid` `profile` `email`.

topics/identity-broker/social/linked-in.adoc

@@ -25,13 +25,13 @@ Click on the `Create Application` button.  This will bring you to the `Create a
 .Create App
 image:../../../images/linked-in-create-app.png[]
 
-Use any value for `Application Name`, `Website URL`, `Description`, `Developer Contact Email` and `Phone` you want.
+Use any value for `Company Name`, `Name`, `Description`, and `Application Use`.
-Select `r_basicprofile` and `r_emailaddress` in the `Default Scope` section.
+Click the `Submit` button.  This will bring you to the new application's settings page.
-Click the `Add Application` button.  This will bring you to the new application's settings page.
 
 .App Settings
 image:../../../images/linked-in-app-settings.png[]
 
+Select `r_basicprofile` and `r_emailaddress` in the `Default Application Permissions` section.
 You'll have to copy the `Redirect URI` from the {{book.project.name}} `Add Identity Provider` page and enter it into the
 `OAuth 2.0` `Authorized Redirect URLs` field on the LinkedIn app settings page.  Don't forget to click `Update` button after
 you do this!

topics/identity-broker/social/stack-overflow.adoc

@@ -16,7 +16,7 @@ NOTE: StackOverflow often changes the look and feel of application registration,
 .Register Application
 image:../../../images/stack-overflow-app-register.png[]
 
-Enter in the application name and the dns domain name of your application and click `Register your Application`.  Type in anything you want
+Enter in the application name and the OAuth Domain Name of your application and click `Register your Application`.  Type in anything you want
 for the other items.
 
 .Settings

topics/identity-broker/social/twitter.adoc

@@ -11,7 +11,7 @@ You can't click save yet, as you'll need to obtain a `Client ID` and `Client Sec
 page is the `Redirect URI`.  You'll have to provide that to Twitter when you register {{book.project.name}} as a client there, so
 copy this URI to your clipboard.
 
-To enable login with Twtter you first have to create an application in the https://dev.twitter.com/apps[Twitter Developer Console].
+To enable login with Twtter you first have to create an application in the https://dev.twitter.com/apps[Twitter Application Management].
 
 .Register Application
 image:../../../images/twitter-app-register.png[]