Merge pull request #35 from ale8k/css-6250/content-alignment-followup

Content Alignment Followup

.custom_wordlist.txt

@@ -55,6 +55,7 @@ NodePort
 ntp
 OAuth
 OAuth2
+OAuth2.0
 observability
 OEM
 OIDC

explanation/jaas_overview.rst

@@ -3,19 +3,30 @@ JAAS Overview
 
 What is JAAS?
 -------------
+To detail what JAAS is, let's look at what JAAS provides:
 
-**JAAS** provides a single location to manage your Juju infrastructure by using the 
-Dashboard or using the same Juju CLI commands to create a high-level overview and 
-the ability to drill-in to the details when you need it.
+- **JAAS** provides a single location to manage your Juju infrastructure by using the 
+  Dashboard or using the same Juju CLI commands to create a high-level overview and 
+  the ability to drill-in to the details when you need it. 
 
+- **JAAS** is  useful for organisations running their own Juju infrastructure 
+  giving them a single point of contact for their entire real estate and, in combination
+  with the Juju Dashboard, giving them a clear overview of their infrastructure.
+
+- **JAAS** enables site reliability engineers and developers to access models via identities from an external IdP
+  and is not limited to local users.
+
+- **JAAS** enables site reliability engineers and developers to manage access control across all of their
+  controllers, models, applications and application offers from a single place, as opposed
+  to having to go through each Juju controller manually and updating permissions specifically
+  for individual local users on each controller.
+
+- As **JAAS** provides a single point of contact for customers entire real estate, automation
+  is substantially easier, automation need only perform actions through **JAAS** and not consult
+  each controller individually.
+
+- **JAAS** can query across multiple models at once, giving deeper insights into your estate.
 
-**JAAS** is useful for customers that do not want to maintain their own controllers
-in public clouds. Canonical's JAAS enables users to deploy their workloads
-in public clouds without the extra complexity and costs associated with running their
-own Juju controllers. JAAS is also useful for organisations 
-running their own Juju infrastructure giving them a single point of contact for 
-their entire real estate and, in combination with the Juju Dashboard, giving
-them a clear overview of their infrastructure.
 
 Architecture
 ------------
@@ -45,5 +56,5 @@ other tools, like the Juju Dashboard or Juju CLI, that communicate with a
 Juju Controller to work seamlessly with JIMM.
 
 For authentication of users or service accounts, JAAS requires an *OIDC Provider*
-(Hydra) that handles the standard OAuth flows including browser flow, device flow,
+(Hydra) that handles the standard OAuth2.0 flows including browser flow, device flow,
 and client credentials.

how-to/use_terraform.rst

@@ -11,7 +11,7 @@ Prerequisites
 
 For this how-to you will need the following:
 
-- An identity provider that can be used to create OAuth2 client credentials.
+- An identity provider that can be used to create OAuth2.0 client credentials.
 - Client credentials (``client_id`` and ``client_secret``) generated by the above identity provider.
 - A deployed JIMM configured to trust the identity provider. For instructions on 
   how to deploy JIMM read :doc:`deploy_jimm`.