docs: replace PerHost/Broadcast scope wording with target language

Swap the remaining internal scope-model terms (PerHost, Broadcast-scoped) for
the product's target vocabulary — Network, Daemon host, Remote hosts — in the
credentials, discovery, docker-proxy, and podman pages. Left unrelated uses of
'broadcast' (ARP) and 'per-host' (error/IP-scoping) alone.

Author: mayanayza

docs/content/docs/guides/docker-proxy.mdx

@@ -100,7 +100,7 @@ Once your proxy is running, create a credential in Scanopy so the daemon knows h
 
 ### Assigning to a host
 
-Docker Proxy is a **PerHost** credential — it must be assigned to the specific host where you want Docker discovery.
+A Docker Proxy credential targets a specific host — the **Daemon host** or a **Remote host** — so assign it to the host where you want Docker discovery.
 
 **For new hosts** (not yet discovered): Add the credential during daemon setup or from the discovery **Credentials** tab, along with the target IP of the Docker host. The credential will be [auto-assigned](/using-scanopy/credentials/#auto-assignment) after the first scan discovers the host.
 

docs/content/docs/guides/podman.mdx

@@ -73,7 +73,7 @@ Create a credential in Scanopy so the daemon knows how to connect.
 
 ### Assigning to a host
 
-Podman credentials are **PerHost** — assign them to the specific host where you want Podman discovery.
+Podman credentials target a specific host — the **Daemon host** (for a local socket) or a **Remote host** — so assign them to the host where you want Podman discovery.
 
 **For new hosts** (not yet discovered): Add the credential during daemon setup (the **Integrations** step) or from the discovery **Credentials** tab, targeting the host by IP — or the daemon host itself (`127.0.0.1`) for a local socket. The credential is [auto-assigned](/using-scanopy/credentials/#auto-assignment) after the first scan discovers the host.
 

docs/content/docs/using-scanopy/credentials.mdx

@@ -23,7 +23,7 @@ Every credential is pointed at one or more **targets**, which determine the host
 | **Daemon host** | The daemon's own machine (`127.0.0.1`). Used for local Docker and Podman sockets. |
 | **Remote hosts** | Specific hosts you name by IP address. |
 
-Not every type supports every target — the **Can be targeted at** column above shows which. SNMP can be a network default or per-host. Docker and Podman are per-host: a **Proxy** credential can point at the daemon host or a remote host, while a **Socket** credential applies only to the daemon's own host.
+Not every type supports every target — the **Can be targeted at** column above shows which. SNMP can target the whole **Network** or specific hosts. Docker and Podman target specific hosts only: a **Proxy** credential can point at the **Daemon host** or a **Remote host**, while a **Socket** credential applies only to the **Daemon host**.
 
 ## How to Provide Credentials
 
@@ -36,7 +36,7 @@ When creating a new daemon, the **Integrations** step lets you add SNMP, Docker,
 - **Target All Hosts** — the credential becomes a network default, tried on every host the daemon scans.
 - **Target Specific Hosts** — the credential applies only to the hosts you name. Add the **daemon host** itself (its loopback address, `127.0.0.1` — used for local Docker and Podman sockets) or one or more **remote hosts** by IP.
 
-After the daemon's first scan discovers hosts at those IPs, per-host credentials are [auto-assigned](/using-scanopy/credentials/#auto-assignment) to the matching hosts and used in subsequent scans without manual assignment.
+After the daemon's first scan discovers hosts at those IPs, host-targeted credentials are [auto-assigned](/using-scanopy/credentials/#auto-assignment) to the matching hosts and used in subsequent scans without manual assignment.
 
 ### From the discovery modal (existing daemons, new network segments)
 

docs/content/docs/using-scanopy/discovery.mdx

@@ -93,7 +93,7 @@ Without SNMP, hosts have only what port scanning and DNS provide — IP addresse
 When the daemon queries a host via SNMP, it resolves which community string to use in this order:
 
 1. **Host-specific assignment** — a credential assigned directly to the host
-2. **Network default** — a Broadcast-scoped credential assigned to the host's network
+2. **Network default** — a credential targeted at the host's whole network (the **Network** target)
 3. **Fallback** — the community string `public`
 
 <Callout type="info">