diff --git a/SUMMARY.adoc b/SUMMARY.adoc
index 2ca34fac6a..ac821e6db2 100644
--- a/SUMMARY.adoc
+++ b/SUMMARY.adoc
@@ -1,6 +1,5 @@
 = Summary
 
-. link:README.adoc[Introduction]
 . link:topics/overview.adoc[Overview]
 .. link:topics/overview/features.adoc[Features]
 .. link:topics/overview/how.adoc[How Does Security Work?]
diff --git a/topics/MigrationFromOlderVersions.adoc b/topics/MigrationFromOlderVersions.adoc
index 0a733ace76..779c014632 100644
--- a/topics/MigrationFromOlderVersions.adoc
+++ b/topics/MigrationFromOlderVersions.adoc
@@ -166,14 +166,14 @@ The version specific section below will mention if any changes are required to a
 
 ==== Migrating to 2.2.0
 
-====== `databaseSchema` property deprecated
+===== `databaseSchema` property deprecated
 
 The `databaseSchema` property for both JPA and Mongo is now deprecated and has been replaced by `initializeEmpty`
 and `migrationStrategy`. `initializeEmpty` can bet set to `true` or `false` and controls if an empty database should
 be initialized. `migrationStrategy` can be set to `update`, `validate` and `manual`. `manual` is only supported for
 relational databases and will write an SQL file with the required changes to the database schema.
 
-====== Changes in Client's Valid Redirect URIs
+===== Changes in Client's Valid Redirect URIs
 The following scenarios are affected:
 
 * When a Valid Redirect URI with query component is saved in a Client (e.g. `\http://localhost/auth?foo=bar`), `redirect_uri` in authorization request must exactly match this URI (or other registered URI in this Client).
@@ -181,13 +181,13 @@ The following scenarios are affected:
 * Wildcards in registered Valid Redirect URIs are no longer supported when query component is present in this URI, so the `redirect_uri` needs to exactly match this saved URI as well.
 * Fragments in registered Valid Redirect URIs (like `\http://localhost/auth#fragment`) are no longer allowed.
 
-====== Authenticate by default removed from Identity Providers
+===== Authenticate by default removed from Identity Providers
 
 Identity providers no longer has an option to set it as a default authenticaton provider. Instead go to Authentication, select the `Browser` flow and configure the `Identity Provider Redirector`. It has an option to set the default identity provider.
 
 ==== Migrating to 2.0.0
 
-====== Upgrading from 1.0.0.Final no longer supported
+===== Upgrading from 1.0.0.Final no longer supported
 
 Upgrading from 1.0.0.Final is no longer supported. To upgrade to this version upgrade to 1.9.8.Final prior to upgrading
 to 2.0.0.
diff --git a/topics/authentication/flows.adoc b/topics/authentication/flows.adoc
index 3fbc1a8742..b9e7f6eb54 100644
--- a/topics/authentication/flows.adoc
+++ b/topics/authentication/flows.adoc
@@ -46,7 +46,7 @@ This is better described in an example.  Let's walk through the `browser` authen
   This is marked as _optional_.  If the user has OTP set up, then this authentication type must run and be successful.  If the user doesn't
   have OTP set up, this authentication type is ignored.
 
-{% if book.product %}
+{% if book.community %}
 === Executions
 
 Executions can be used