Update doc to reflect change in FAB-18163 (#1729)

Signed-off-by: Jason Yellick <jyellick@us.ibm.com>
(cherry picked from commit 9881a25)

Co-authored-by: Jason Yellick <jyellick@us.ibm.com>

docs/source/raft_configuration.md

@@ -122,16 +122,9 @@ used to further fine tune the cluster communication or replication mechanisms:
    To recover from such a scenario, it is possible to make TLS handshakes
    between ordering nodes consider the time to be shifted backwards a given
    amount that is configured to `TLSHandshakeTimeShift`.
-   In order to be as uninvasive as possible, this configuration option
-   only effects ordering nodes that use a separate gRPC server for their
-   intra-cluster communication.
-   If your cluster is communicating via the same gRPC server that is used
-   to service clients and peers, you need to first reconfigure your orderer
-   by additionally setting `general.cluster.ListenPort`, `general.cluster.ListenAddress`,
-   `ServerCertificate` and `ServerPrivateKey`, and then restarting the orderer
-   in order for the new configuration to take effect.
-
-
+   This setting only applies when a separate cluster listener is in use.  If
+   the cluster service is sharing the orderer's main gRPC server, then instead
+   specify `TLSHandshakeTimeShift` in the `General.TLS` section.
 
 **Consensus parameters:**