[enterprise-4.9] [logging-5.3]RHDEVDOCS-2681 Document "Remove legacy configuration mechanism for lo…

logging/cluster-logging-external.adoc

@@ -16,8 +16,6 @@ To send audit logs to the default internal Elasticsearch log store, use the Clus
 
 When you forward logs externally, the Red Hat OpenShift Logging Operator creates or modifies a Fluentd config map to send logs using your desired protocols. You are responsible for configuring the protocol on the external log aggregator.
 
-Alternatively, you can create a config map to use the xref:../logging/cluster-logging-external.html#cluster-logging-collector-legacy-fluentd_cluster-logging-external[Fluentd *forward* protocol] or the xref:../logging/cluster-logging-external.html#cluster-logging-collector-legacy-syslog_cluster-logging-external[syslog protocol] to send logs to external systems. However, these methods for forwarding logs are deprecated in {product-title} and will be removed in a future release.
-
 [IMPORTANT]
 ====
 You cannot use the config map methods and the Cluster Log Forwarder in the same cluster.
@@ -62,9 +60,4 @@ include::modules/cluster-logging-collector-collecting-ovn-logs.adoc[leveloffset=
 
 * xref:../networking/network_policy/logging-network-policy.adoc#nw-networkpolicy-audit-concept_logging-network-policy[Network policy audit logging]
 
-
-include::modules/cluster-logging-collector-legacy-fluentd.adoc[leveloffset=+1]
-
-include::modules/cluster-logging-collector-legacy-syslog.adoc[leveloffset=+1]
-
 include::modules/cluster-logging-troubleshooting-log-forwarding.adoc[leveloffset=+1]