diff --git a/documentation/modules/ROOT/pages/configuration/content-based-routing.adoc b/documentation/modules/ROOT/pages/configuration/content-based-routing.adoc
index 3cc4c21ed..6b49dfa6d 100644
--- a/documentation/modules/ROOT/pages/configuration/content-based-routing.adoc
+++ b/documentation/modules/ROOT/pages/configuration/content-based-routing.adoc
@@ -4,7 +4,7 @@
 // Title: Routing change event records to topics according to event content
 [id="content-based-routing"]
 = Content-based routing
-
+ifdef::community[]
 :toc:
 :toc-placement: macro
 :linkattrs:
@@ -12,7 +12,7 @@
 :source-highlighter: highlight.js
 
 toc::[]
-
+endif::community[]
 By default, {prodname} streams all of the change events that it reads from a table to a single static topic.
 However, there might be situations in which you might want to reroute selected events to other topics, based on the event content.
 The process of routing messages based on their content is described in the https://www.enterpriseintegrationpatterns.com/patterns/messaging/ContentBasedRouter.html[Content-based routing] messaging pattern. 
diff --git a/documentation/modules/ROOT/pages/configuration/filtering.adoc b/documentation/modules/ROOT/pages/configuration/filtering.adoc
index c98815261..8e99a361c 100644
--- a/documentation/modules/ROOT/pages/configuration/filtering.adoc
+++ b/documentation/modules/ROOT/pages/configuration/filtering.adoc
@@ -4,7 +4,7 @@
 // Title: Filtering Debezium change event records
 [id="message-filtering"]
 = Message Filtering
-
+ifdef::community[]
 :toc:
 :toc-placement: macro
 :linkattrs:
@@ -12,7 +12,7 @@
 :source-highlighter: highlight.js
 
 toc::[]
-
+endif::community[]
 By default, {prodname} delivers every data change event that it receives to the Kafka broker.
 However, in many cases, you might be interested in only a subset of the events emitted by the producer. 
 To enable you to process only the records that are relevant to you, {prodname} provides the _filter_ simple message transform (SMT).