claim -> connect in docs (#19060)

Co-authored-by: Ilya Mashchenko <ilya@netdata.cloud>

README.md

@@ -259,7 +259,7 @@ You can also use Netdata Parents to:
 
 ### 5. **Connect to Netdata Cloud** :cloud:
 
-[Sign-in](https://app.netdata.cloud/sign-in) to [Netdata Cloud](https://www.netdata.cloud/) and claim your Netdata Agents and Parents.
+[Sign-in](https://app.netdata.cloud/sign-in) to [Netdata Cloud](https://www.netdata.cloud/) and connect your Netdata Agents and Parents.
 If you connect your Netdata Parents, there is no need to connect your Netdata Agents. They will be connected via the Parents.
 
 When your Netdata nodes are connected to Netdata Cloud, you can (on top of the above):

docs/dashboards-and-charts/README.md

@@ -25,7 +25,7 @@ The Netdata dashboard consists of the following main sections:
 
 > **Note**
 >
-> Some sections of the dashboard, when accessed through the Agent, may require the user to be signed in to Netdata Cloud or have the Agent claimed to Netdata Cloud for their full functionality. Examples include saving visualization settings on charts or custom dashboards, claiming the node to Netdata Cloud, or executing functions on an Agent.
+> Some dashboard sections may require the user to be signed in and have the Agent connected to Netdata Cloud for their full functionality when accessed through the Agent. Examples include saving visualization settings on charts or custom dashboards, connecting a node to Netdata Cloud, or executing functions on an Agent.
 
 ## How to access the dashboards?
 

docs/deployment-guides/deployment-strategies.md

@@ -24,7 +24,7 @@ An API key is a key created with `uuidgen` and is used for authentication and/or
 
 #### Child config
 
-As mentioned above, we do not recommend to claim the Child to Cloud directly during your setup.
+As mentioned above, we do not recommend to connect the Child to Cloud directly during your setup.
 
 This is done in order to reduce the footprint of the Netdata Agent on your production system, as some capabilities can be switched OFF for the Child and kept ON for the Parent.
 

docs/deployment-guides/standalone-deployment.md

@@ -134,7 +134,7 @@ flowchart LR
 
 ### Configuration steps for standalone Netdata Agents with Netdata Cloud
 
-- Install Netdata Agents using the commands given by Netdata Cloud, so that they will be automatically connected to your Netdata Cloud space. Otherwise, install Netdata Agents and then claim them via the command line or their dashboard.
+- Install Netdata Agents using the commands given by Netdata Cloud so that they will be automatically connected to your Space. Otherwise, install Netdata Agents and connect them via the command line or their dashboard.
 
 - Optionally: disable their direct dashboard access to secure them.
 

docs/glossary.md

@@ -149,4 +149,4 @@ even thousands of nodes. There are no actual bottlenecks especially if you retai
 
 ## Z
 
-- **Zero Configuration**: Netdata is pre-configured and capable to autodetect and monitor any well known application that runs on your system. You just deploy and claim Netdata Agents in your Netdata space, and monitor them in seconds.
+- **Zero Configuration**: Netdata is pre-configured and capable to autodetect and monitor any well-known application that runs on your system. You just deploy and connect Netdata Agents in your Netdata space, and monitor them in seconds.

docs/security-and-privacy-design/netdata-agent-security.md

@@ -32,8 +32,8 @@ configures it.
 
 The Netdata Agent's web API can also use TLS if configured.
 
-When Netdata Agents are claimed to Netdata Cloud, the communication happens via MQTT over Web Sockets over TLS, and
-public/private keys are used for authorizing access. These keys are exchanged during the claiming process (usually
+When Netdata Agents are connected to the Cloud, the communication happens via MQTT over Web Sockets over TLS, and
+public/private keys are used for authorizing access. These keys are exchanged during the connecting process (usually
 during the provisioning of each Agent).
 
 ## Authentication

docs/top-monitoring-netdata-functions.md

@@ -13,7 +13,7 @@ For more details please check out documentation on how we use our internal colle
 
 The following is required to be able to run Functions from Netdata Cloud.
 
-- At least one of the nodes claimed to your Space should be on a Netdata Agent version higher than `v1.37.1`
+- At least one of the nodes connected to your Space should be on a Netdata Agent version higher than `v1.37.1`
 - Ensure that the node has the collector that exposes the function you want enabled
 
 ## What functions are currently available?

integrations/deploy.yaml

@@ -9,7 +9,7 @@
   keywords:
     - linux
   most_popular: true
-  install_description: "Run the following command on your node to install and claim Netdata:"
+  install_description: "Run the following command on your node to install and connnect Netdata to your Space:"
   methods:
     - &ks_wget
       method: wget

packaging/docker/README.md

@@ -135,7 +135,7 @@ volumes:
 
 > :bookmark_tabs: Note
 >
-> If you plan to Claim the node to Netdata Cloud, you can find the command with the right parameters by clicking the "
+> If you plan to connect the node to Netdata Cloud, you can find the command with the right parameters by clicking the "
 > Add Nodes" button in your Space's "Nodes" view.
 
 ### With systemd units monitoring
@@ -531,7 +531,7 @@ docker run -d --name=netdata \
 
 > :bookmark_tabs: Note
 >
-> If you plan to Claim the node to Netdata Cloud, you can find the command with the right parameters by clicking the "
+> If you plan to connect the node to Netdata Cloud, you can find the command with the right parameters by clicking the "
 > Add Nodes" button in your Space's "Nodes" view.
 
 ## Docker tags

packaging/installer/methods/freebsd.md

@@ -118,7 +118,7 @@ The following options are mutually exclusive and specify special operations othe
 - `--reinstall-even-if-unsafe`: If there is an existing install, reinstall it instead of trying to update it, even if doing so is known to potentially break things (for example, if we cannot detect what type of installation it is). If there is not an existing install, install Netdata normally.
 - `--reinstall-clean`: If there is an existing install, uninstall it before trying to install Netdata. Fails if there is no existing install.
 - `--uninstall`: Uninstall an existing installation of Netdata. Fails if there is no existing install.
-- `--claim-only`: If there is an existing install, only try to claim it without attempting to update it. If there is no existing install, install and claim Netdata normally.
+- `--claim-only`: If there is an existing install, only try to connect it without attempting to update it. If there is no existing install, install and connect Netdata normally.
 - `--repositories-only`: Only install repository configuration packages instead of doing a full install of Netdata. Automatically sets --native-only.
 - `--prepare-offline-install-source`: Instead of installing the Agent, prepare a directory that can be used to install on another system without needing to download anything. See our [offline installation documentation](/packaging/installer/methods/offline.md) for more info.
 

packaging/installer/methods/kickstart.md

@@ -112,7 +112,7 @@ By default, the script installs a cron job to automatically update Netdata to th
 By default, the kickstart script will provide a Netdata Agent installation that can potentially communicate with Netdata Cloud if the Netdata Agent is further configured to do so.
 
 - `--claim-token`
-  Specify a unique claiming token associated with your Space in Netdata Cloud to be used to connect to the node after the installation. This will connect and claim the Netdata Agent to Netdata Cloud.
+  Specify a unique claiming token associated with your Space in Netdata Cloud to be used to connect to the node after the installation. This will connect and connect the Netdata Agent to Netdata Cloud.
 - `--claim-url`
   Specify a URL to use when connecting to the Cloud. Defaults to `https://app.netdata.cloud`. Use this option to change the Netdata Cloud URL to point to your Netdata Cloud installation.
 - `--claim-rooms`
@@ -120,7 +120,7 @@ By default, the kickstart script will provide a Netdata Agent installation that
 - `--claim-proxy`
   Specify a proxy to use when connecting to the Cloud in the form of `http://[user:pass@]host:ip` for an HTTP(S) proxy. See [connecting through a proxy](/src/claim/README.md#automatically-via-a-provisioning-system-or-the-command-line) for details.
 - `--claim-only`
-  If there is an existing installation, only try to claim it without attempting to update it. If there is no existing installation, install and claim Netdata normally.
+  If there is an existing installation, only try to connect it without attempting to update it. If there is no existing installation, install and connect Netdata normally.
 
 ### anonymous telemetry
 

packaging/installer/methods/macos.md

@@ -49,7 +49,7 @@ curl https://get.netdata.cloud/kickstart.sh > /tmp/netdata-kickstart.sh && sh /t
 
 The Netdata Agent is installed under `/usr/local/netdata` on your machine. Your machine will also show up as a node in your Netdata Cloud.
 
-If you experience issues while claiming your node, follow the steps in our [Troubleshoot](/src/claim/README.md#troubleshoot) documentation.
+If you experience issues while connecting your node, follow the steps in our [Troubleshoot](/src/claim/README.md#troubleshoot) documentation.
 
 ## Install Netdata via Homebrew
 

packaging/windows/WINDOWS_INSTALLER.md

@@ -47,7 +47,7 @@ Connect your Agent to your Netdata Cloud Space with token `<YOUR_TOKEN>` and roo
 msiexec /qn /i netdata-x64.msi TOKEN="<YOUR_TOKEN>" ROOMS="<YOUR_ROOM>"
 ```
 
-Replace `<YOUR_TOKEN>` and `<YOUR_ROOM>` with your Netdata Cloud Space claim token and room ID, respectively.
+Replace `<YOUR_TOKEN>` and `<YOUR_ROOM>` with your Space claim token and Room ID, respectively.
 
 > **Note**
 >

src/claim/README.md

@@ -1,8 +1,6 @@
 # Connect Agent to Cloud
 
-This section guides you through installing and securely connecting a new Netdata Agent to Netdata Cloud via the
-encrypted Agent-Cloud Link ([ACLK](/src/aclk/README.md)). Connecting your Agent to Netdata Cloud unlocks additional
-features like centralized monitoring and easier collaboration.
+This section guides you through installing and securely connecting a new Agent to Netdata Cloud via the encrypted Agent-Cloud Link ([ACLK](/src/aclk/README.md)). Connecting your Agent to Netdata Cloud unlocks additional features like centralized monitoring and easier collaboration.
 
 ## Connect
 
@@ -14,8 +12,7 @@ There are two places in the UI where you can add/connect your Node:
   select "Nodes." Click the "+" button to add a new node.
 - [**Nodes tab**](/docs/dashboards-and-charts/nodes-tab.md): Click on the "Add nodes" button.
 
-Netdata Cloud will generate a command that you can execute on your Node to install and claim the Agent. The command is
-available for different installation methods:
+Netdata Cloud will generate a command that you can execute on your Node to install and connect the Agent to your Space. The command is available for different installation methods:
 
 | Method              | Description                                                                                                                                                                                                      |
 |---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
@@ -70,10 +67,9 @@ example:
    insecure = no
 ```
 
-If the Agent is already running, you can either run `netdatacli reload-claiming-state` or restart the Agent.
-Otherwise, the Agent will be claimed when it starts.
+If the Agent is already running, you can either run `netdatacli reload-claiming-state` or restart the Agent. Otherwise, the Agent will be connected when it starts.
 
-If the claiming process fails, the reason will be logged in daemon.log (search for "CLAIM") and the `cloud` section of `http://ip:19999/api/v2/info`.
+If the connection process fails, the reason will be logged in daemon.log (search for "CLAIM") and the `cloud` section of `http://ip:19999/api/v2/info`.
 
 #### Automatically, via environment variables
 
@@ -85,9 +81,9 @@ Netdata will use the following environment variables:
 - `NETDATA_CLAIM_PROXY`: The URL of a proxy server to use for the connection (optional)
 - `NETDATA_EXTRA_CLAIM_OPTS`, may contain a space separated list of options. The option `-insecure` is the only currently used.
 
-The `NETDATA_CLAIM_TOKEN` alone is enough for triggering the claiming process.
+The `NETDATA_CLAIM_TOKEN` alone is enough for triggering the connection process.
 
-If the claiming process fails, the reason will be logged in daemon.log (search for "CLAIM") and the `cloud` section of `http://ip:19999/api/v2/info`.
+If the connection process fails, the reason will be logged in daemon.log (search for "CLAIM") and the `cloud` section of `http://ip:19999/api/v2/info`.
 
 ## Reconnect