Update resilience-app-development-overview.md

Author: v-edmckillop

articles/active-directory/fundamentals/resilience-app-development-overview.md

@@ -1,6 +1,6 @@
 ---
 title: Increase the resilience of authentication and authorization applications you develop
-description: Overview of our resilience guidance for application development using Azure Active Directory and the Microsoft identity platform
+description: Resilience guidance for application development using Azure Active Directory and the Microsoft identity platform
 services: active-directory 
 ms.service: active-directory
 ms.subservice: fundamentals 
@@ -14,14 +14,19 @@ ms.date: 03/02/2023
 
 # Increase the resilience of authentication and authorization applications you develop
 
-Microsoft Identity uses modern, token-based authentication and authorization. This means that a client application acquires tokens from an Identity provider to authenticate the user and to authorize the application to call protected APIs. A service will validate tokens.
+The Microsoft identity platform helps you build applications your users and customers can sign in to using their Microsoft identities or social accounts. Microsoft identity platform uses token-based authentication and authorization. Client application acquire tokens from an identity provider (IdP) to authenticate users and authorize applications to call protected APIs. A service validates tokens.
 
-A token is valid for a certain length of time before the app must acquire a new one. Rarely, a call to retrieve a token could fail due to an issue like network or infrastructure failure or authentication service outage. In this document, we outline steps a developer can take to increase resilience in their applications if a token acquisition failure occurs.
+Learn more: 
 
-These articles provide guidance on increasing resiliency in apps using the Microsoft identity platform and Azure Active Directory. There is guidance for both for client and service applications that work on behalf of a signed in user as well as daemon applications that work on their own behalf. They contain best practices for using tokens as well as calling resources.
+[What is the Microsoft identity platform?](../develop/v2-overview.md)
+[Security tokens](../develop/security-tokens.md)
 
-- [Build resilience into applications that sign-in users](resilience-client-app.md)
-- [Build resilience into applications without users](resilience-daemon-app.md)
+A token is valid for a length of time, and then the app must acquire a new one. Rarely, a call to retrieve a token fails due to network or infrastructure issues or an authentication service outage. In this article, you'll find a list of articles to help increase resilience in applications.
+
+The following articles have guidance for client and service applications for a signed in user and daemon applications. They contain best practices for using tokens and calling resources.
+
+- [Increase the resilience of authentication and authorization in client applications you develop](resilience-client-app.md)
+- [Increase the resilience of authentication and authorization in daemon applications you develop](resilience-daemon-app.md)
 - [Build resilience in your identity and access management infrastructure](resilience-in-infrastructure.md)
-- [Build resilience in your CIAM systems](resilience-b2c.md)
-- [Build services that are resilient to metadata refresh](../develop/howto-build-services-resilient-to-metadata-refresh.md)
+- [Build resilience in your customer identity and access management with Azure AD B2C](resilience-b2c.md)
+- [Build services that are resilient to Azure AD's OpenID Connect metadata refresh](../develop/howto-build-services-resilient-to-metadata-refresh.md)