[ZT] clarify target hostname (#23524)

* clarify target hostname

* tweak wording

Author: ranbel

src/content/glossary/cloudflare-one.yaml

@@ -207,6 +207,10 @@ entries:
     general_definition: |-
       a resource with an IP address or hostname that is reachable by Cloudflare, such as a server or web application.
 
+  - term: target hostname
+    general_definition: |-
+      a label used to identify a set of targets in an Access for Infrastructure application.
+
   - term: team domain
     general_definition: |-
       a unique subdomain assigned to your Cloudflare account (for example, `<your-team-name>.cloudflareaccess.com`), where users will find the apps you have secured behind Cloudflare Zero Trust.

src/content/partials/cloudflare-one/access/add-infrastructure-app.mdx

@@ -2,15 +2,15 @@
 {}
 ---
 
-import { Tabs, TabItem, Render, APIRequest } from "~/components";
+import { Tabs, TabItem, Render, APIRequest, GlossaryTooltip } from "~/components";
 
 <Tabs syncKey="dashPlusAPI">
 <TabItem label="Dashboard">
 1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Access** > **Applications**.
 2. Select **Add an application**.
 3. Select **Infrastructure**.
 4. Enter any name for the application.
-5. In **Target criteria**, select the target hostname(s) that will represent the application. The application definition will apply to all targets that share the selected hostname, including any targets added in the future.
+5. In **Target criteria**, select the <GlossaryTooltip term="target hostname">target hostname(s)</GlossaryTooltip> that you want to secure. This application definition will apply to all targets that share the selected hostname, including any targets added in the future. Similarly, if you later decide to change the hostname for a target, the renamed target will no longer be covered by this application.
 6. Enter the **Protocol** and **Port** that will be used to connect to the server.
 7. (Optional) If a protocol runs on more than one port, select **Add new target criteria** and reconfigure the same target hostname and protocol with a different port number.
 	:::note

src/content/partials/cloudflare-one/access/add-target.mdx

@@ -3,7 +3,7 @@ params:
   - protocol
 ---
 
-import { Tabs, TabItem, Render, Details, APIRequest} from "~/components";
+import { Tabs, TabItem, Render, Details, APIRequest, GlossaryTooltip } from "~/components";
 
 A target represents a single resource in your infrastructure (such as a server, Kubernetes cluster, database, or container) that users will connect to through Cloudflare.
 
@@ -18,7 +18,7 @@ To create a new target:</p>) :
 <TabItem label="Dashboard">
 1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Networks** > **Targets**.
 2. Select **Add a target**.
-3. In **Target hostname**, enter a user-friendly name for the target resource. We recommend using the server hostname, for example `production-server`. The hostname does not need to be unique and can be reused for multiple targets. Hostnames are used to define the subset of targets included in an infrastructure application and are not used in DNS address resolution.
+3. In **Target hostname**, enter a user-friendly name for the <GlossaryTooltip term="target">target</GlossaryTooltip>. We recommend using the server hostname, for example `production-server`. The target hostname does not need to be unique and can be reused for multiple targets. Hostnames are used to define the targets secured by an Access application; they are not used for DNS address resolution.
 	<Details header="Format restrictions">
 			- Case insensitive
 			- Contain no more than 253 characters