diff --git a/documentation/modules/ROOT/pages/developer-resources.adoc b/documentation/modules/ROOT/pages/developer-resources.adoc
index afa83b7..8343bf5 100644
--- a/documentation/modules/ROOT/pages/developer-resources.adoc
+++ b/documentation/modules/ROOT/pages/developer-resources.adoc
@@ -1,7 +1,8 @@
-= Solution Patterns: Event Driven API Management
+
 :sectnums:
 :sectlinks:
 :doctype: book
+= Solution Patterns: Event Driven API Management
 
 
 = Developer Resources
diff --git a/documentation/modules/ROOT/pages/index.adoc b/documentation/modules/ROOT/pages/index.adoc
index 29ee8d4..040ee4c 100644
--- a/documentation/modules/ROOT/pages/index.adoc
+++ b/documentation/modules/ROOT/pages/index.adoc
@@ -11,7 +11,7 @@ Rather than the synchronous request-response pattern of RESTful APIs,event-drive
 
 The solution leverages https://www.redhat.com/en/resources/application-foundations-datasheet[Red Hat Application Foundations^] components to build a scalable webhook delivery system. This system pushes internal events from your event broker (Kafka) to your API consumers, allowing you to manage events as an API product by applying API management practices to an event-driven API product.
 
-*Contributors:* Abdelhamid Soliman
+*Contributors:* Abdelhamid Soliman (Red Hat)
 
 ++++
  <br>