Fix - Is IP the correct abbreviation for Identity Provider #10883 (#11435)

* Update claims-based-identity-model.md

Fix #10883

* Update docs/framework/security/claims-based-identity-model.md

Co-Authored-By: msschl <markus_schlotbohm@as-gmbh.de>

* Update docs/framework/security/claims-based-identity-model.md

Co-Authored-By: msschl <markus_schlotbohm@as-gmbh.de>

Author: msschl

docs/framework/security/claims-based-identity-model.md

@@ -67,10 +67,10 @@ When you build claims-aware applications, the user identity is represented in yo
 
  This diagram shows a Web site (the relying party application, RP) that has been configured to use WIF for authentication and a client, a web browser, that wants to use that site.  
 
-1.  When an unauthenticated user requests a page their browser is redirected to the identity provider (IP) pages.  
+1.  When an unauthenticated user requests a page, their browser is redirected to the identity provider (IdP) pages.  
 
-2.  The IP requires the user to present their credentials, e.g. username/password, Kerberos, etc.  
+2.  The IdP requires the user to present their credentials, such as username/password or Kerberos authentication.  
 
-3.  The IP issues a token back to that is returned to the browser.  
+3.  The IdP issues a token back to that is returned to the browser.  
 
 4.  The browser is now redirected back to the originally requested page where WIF determines if the token satisfies the requirements to access the page. If so a cookie is issued to establish a session so the authentication only needs to occur once, and control is passed to the application.