OSDOCS-349 Update glossary reference from router to Ingress

contributing_to_docs/term_glossary.adoc

@@ -213,6 +213,25 @@ The file that Ignition uses to configure Red Hat Enterprise Linux CoreOS during
 operating system initialization. The installation program generates different
 Ignition config files to initialize bootstrap, master, and worker nodes.
 
+=== Ingress
+
+Usage: Ingress
+
+API object that allows developers to expose Services through an HTTP(S) aware
+load balancing and proxy layer via a public DNS entry. The Ingress resource may
+further specify TLS options and a certificate, or specify a public CNAME that
+the OpenShift Ingress Controller should also accept for HTTP and HTTPS traffic.
+An administrator typically configures their Ingress Controller to be visible
+outside the cluster firewall, and may also add additional security, caching, or
+traffic controls on the Service content.
+
+=== Ingress Controller
+
+Usage: Ingress Controller(s)
+
+A resource that forwards traffic to endpoints of Services. The Ingress Controller
+replaces router from {product-title} 3 and earlier.
+
 == K
 
 ''''
@@ -392,11 +411,11 @@ Usage: Route(s)
 
 OpenShift-specific API object that allows developers to expose Services through
 an HTTP(S) aware load balancing and proxy layer via a public DNS entry. The
-Route may further specify TLS options and a certificate, or specify a public
-CNAME that the OpenShift router should also accept for HTTP and HTTPS traffic.
-An administrator typically configures their router to be visible outside the
-cluster firewall, and may also add additional security, caching, or traffic
-controls on the Service content.
+route may further specify TLS options and a certificate, or specify a public
+CNAME that the OpenShift Ingress Controller should also accept for HTTP and
+HTTPS traffic. An administrator typically configures their Ingress Controller to
+be visible outside the cluster firewall, and may also add additional security,
+caching, or traffic controls on the Service content.
 
 == S