Better wording on the ain page

docs/azure-saas-docs/content/en/_index.md

@@ -10,29 +10,24 @@ weight: 0
 
 The Azure SaaS Development Kit is a deployable reference implementation of pre-built resources designed to help you launch your SaaS offering faster:
 
-* There are standard SaaS components that implement features such as identity, onboarding, and tenant management.
-* 100% [Open-source code](https://github.com/Azure/azure-saas), allowing developers to build by example or modify/extend to be purpose-built for your particular scenario.
-* Fully documented code makes it clear how the code functions, and how key decisions were made.
+* It includes commonly needed SaaS components that implement features such as identity, onboarding, and tenant management.
+* It is 100% [Open-source code](https://github.com/Azure/azure-saas), allowing you to build by example or modify/extend to be purpose-built for your particular scenario.
+* The code is fully documented, making it clear how the code functions, and why key design decisions were made.
 
-## Who should use this dev kit?
+## Usage Options
 
-We think this kit can provide value in some way to a large number of people in a varying degree of situations, but we had the following scenarios especially in mind when building this project:
+How you use the dev kit is up to you, here are some ideas to get you started:
 
-* Modernizing an existing application to support [full multitenancy](https://docs.microsoft.com/en-us/azure/architecture/guide/multitenant/considerations/tenancy-models#fully-multitenant-deployments) as part of a shift to a SaaS based business model
-* Developing a greenfield SaaS offering for the first time
-* Migrating a SaaS offering from another cloud to Azure
-  
-If your company/team does not fit in one of these scenarios, that's okay! Check out the project anyway and you may find something that could be of use to you.
+* Modernizing an existing application to support [full multitenancy](https://docs.microsoft.com/en-us/azure/architecture/guide/multitenant/considerations/tenancy-models#fully-multitenant-deployments) as part of a shift to a SaaS based business model.
+* Developing a greenfield SaaS offering for the first time.
+* Migrating a SaaS offering from another cloud to Azure.
 
-## How can this dev kit be used?
+This is not a one-size-fits-all solution. Use as little or as much as you like. It is designed to be both a modular deployable reference implementation and also a reference architecture. You are free to use and change the code contained within this project in any way you'd like (following the terms of the license):
 
-The Azure SaaS Dev Kit is designed to be both a modular deployable reference implementation and also a reference architecture. You are free to use and change the code contained within this project in any way you'd like, but we have 3 main ways outlined that we see a team choosing to use this:
-
-1. Deploy the entire solution to Azure using the bicep templates we provide, make changes to fit your exact use case, and start building your SaaS application in the stub app we provide
-
-2. Deploy one or more of our modules and hook it into your existing SaaS application
-
-3. Reference our code & architecture and build something entirely custom using the best practices we outlined
+* Deploy the entire solution to Azure using the bicep templates we provide, make changes to fit your exact use case, and start building your SaaS application from there.
+* Deploy one or more of our modules and hook it into your existing SaaS application.
+* Reference our code & architecture and build something entirely custom using the best practices we outlined.
+* Or, simply gain inspiration from this codebase.
 
 ## Modular Architecture