Update terminology

Author: maxvp

src/content/docs/cloudflare-one/policies/gateway/tiered-policies/index.mdx

@@ -25,16 +25,16 @@ The Gateway Tenant platform supports tiered and siloed account configurations.
 
 ### Tiered accounts
 
-In a tiered account configuration, a top-level parent account enforces global security policies that apply to all of its child accounts. Child accounts can add policies as needed while still being managed by the parent account. Organization owners can also configure child accounts independently from the parent account, including:
+In a tiered account configuration, a top-level source account enforces global security policies that apply to all of its recipient accounts. Recipient accounts can add policies as needed while still being managed by the source account. Organization owners can also configure recipient accounts independently from the source account, including:
 
 - Configuring a [custom block page](/cloudflare-one/policies/gateway/block-page/)
 - Generating or uploading [root certificates](/cloudflare-one/connections/connect-devices/user-side-certificates/)
 - Mapping [DNS locations](/cloudflare-one/connections/connect-devices/agentless/dns/locations/)
 - Creating [lists](/cloudflare-one/policies/gateway/lists/)
 
-Gateway will automatically [generate a unique root CA](/cloudflare-one/connections/connect-devices/user-side-certificates/#generate-a-cloudflare-root-certificate) for each child account in an organization. Each child account is subject to the default Zero Trust [account limits](/cloudflare-one/account-limits/).
+Gateway will automatically [generate a unique root CA](/cloudflare-one/connections/connect-devices/user-side-certificates/#generate-a-cloudflare-root-certificate) for each recipient account in an organization. Each recipient account is subject to the default Zero Trust [account limits](/cloudflare-one/account-limits/).
 
-Gateway evaluates parent account policies before any child account policies. In a Cloudflare Organization, child accounts cannot bypass parent account policies. All traffic and corresponding policies, logs, and configurations for a child account will be contained to that child account. Organization owners can view logs for child accounts on a per-account basis, and [Logpush jobs](/logs/logpush/) must be configured separately.
+Gateway evaluates source account policies before any recipient account policies. In a Cloudflare Organization, recipient accounts cannot bypass source account policies. All traffic and corresponding policies, logs, and configurations for a recipient account will be contained to that recipient account. Organization owners can view logs for recipient accounts on a per-account basis, and [Logpush jobs](/logs/logpush/) must be configured separately.
 
 ```mermaid
 flowchart TD
@@ -43,15 +43,15 @@ flowchart TD
  accDescr: Flowchart describing the order of precedence Gateway applies policies in a tiered account configuration.
 
 %% Flowchart
- subgraph s1["Parent account"]
+ subgraph s1["Source account"]
         n1["Block malware"]
         n2["Block DNS tunnel"]
         n3["Block spyware"]
   end
- subgraph s2["Child account A"]
+ subgraph s2["Recipient account A"]
         n4["Block social media"]
   end
- subgraph s3["Child account B"]
+ subgraph s3["Recipient account B"]
         n5["Block instant messaging"]
   end
     n1 ~~~ n2
@@ -84,7 +84,7 @@ flowchart TD
         n1["Block social media"]
   end
  subgraph s2["Siloed account C"]
-        n2["Block instant messaing"]
+        n2["Block instant messaging"]
   end
  subgraph s3["Siloed account B"]
         n3["Block news"]