Merge pull request #3244 from JacobTanenbaum/InsecureEdgeTermination

adding for docs for insecureEdgeTerminatePolicy in reencrypt and passthrough routes

Author: ahardin-rh

architecture/core_concepts/routes.adoc

@@ -682,6 +682,12 @@ The destination pod is responsible for serving certificates for the
 traffic at the endpoint. This is currently the only method that can support
 requiring client certificates (also known as two-way authentication).
 
+[NOTE]
+====
+passthrough routes can also have an `insecureEdgeTerminationPolicy` the only valid values are 
+`None` or empty (for disabled) or `Redirect`.
+====
+
 [[re-encryption-termination]]
 *Re-encryption Termination*
 
@@ -725,6 +731,11 @@ validate the endpoint certificate, securing the connection from the router to
 the destination. This field is required, but only for re-encryption.
 ====
 
+[NOTE]
+====
+Reencrypt routes can have an insecureEdgeTerminationPolicy with all of the same values as for edge-terminated routes.
+====
+
 
 [[router-sharding]]
 == Router Sharding