[DOCS] Updates X-Pack terminology (#28208)

docs/setup/production.asciidoc

@@ -1,9 +1,9 @@
 [[production]]
 == Using Kibana in a production environment
 
-* <<configuring-kibana-shield, Using Kibana with {xpack}>>
-* <<enabling-ssl, Enabling SSL>>
-* <<load-balancing, Load balancing across multiple {es} nodes>>
+* <<configuring-kibana-shield>>
+* <<enabling-ssl>>
+* <<load-balancing>>
 
 How you deploy Kibana largely depends on your use case. If you are the only user,
 you can run Kibana on your local machine and configure it to point to whatever
@@ -19,19 +19,19 @@ and an Elasticsearch client node on the same machine. For more information, see
 
 [float]
 [[configuring-kibana-shield]]
-=== Using Kibana with {security}
+=== Using {stack} {security-features}
 
-You can use {stack-ov}/elasticsearch-security.html[{security}] to control what
-Elasticsearch data users can access through Kibana.
+You can use {stack-ov}/elasticsearch-security.html[{stack} {security-features}] 
+to control what {es} data users can access through Kibana.
 
-When {security} is enabled, Kibana users have to log in. They need to
+When {security-features} are enabled, Kibana users have to log in. They need to
 have the `kibana_user` role as well as access to the indices they
 will be working with in Kibana.
 
 If a user loads a Kibana dashboard that accesses data in an index that they
 are not authorized to view, they get an error that indicates the index does
-not exist. {security} does not currently provide a way to control which
-users can load which dashboards.
+not exist. The {security-features} do not currently provide a way to control 
+which users can load which dashboards.
 
 For information about setting up Kibana users, see
 {kibana-ref}/using-kibana-with-security.html[Configuring security in Kibana].