Ingest New Documentation (#2780)

Co-authored-by: netdatabot <43409846+netdatabot@users.noreply.github.com>

Author: github-actions[bot]

docs/Getting Started.mdx

@@ -110,7 +110,7 @@ Once logged into Netdata Cloud, you'll see connection instructions. There are th
 All methods will show you a command like this:
 
 ```bash
-bash <(curl -Ss https://my-netdata.io/kickstart.sh) --claim-token YOUR_TOKEN --claim-rooms YOUR_ROOMS --claim-url https://app.netdata.cloud
+bash <(curl -Ss https://get.netdata.cloud/kickstart.sh) --claim-token YOUR_TOKEN --claim-rooms YOUR_ROOMS --claim-url https://app.netdata.cloud
 ```
 
 :::
@@ -238,7 +238,7 @@ Click "Invite Users" in your Space sidebar to add team members. Set appropriate
 **Organize by Your Needs:**
 
 | **Category**       | **Examples**                         |
-|--------------------|--------------------------------------|
+| ------------------ | ------------------------------------ |
 | **By Service**     | Web servers, databases, applications |
 | **By Location**    | Data centers, cloud regions          |
 | **By Team**        | DevOps, SRE, development teams       |
@@ -258,7 +258,7 @@ Click "Invite Users" in your Space sidebar to add team members. Set appropriate
 ### Traditional Monitoring vs Netdata Business
 
 | **Traditional Monitoring**                       |        | **Netdata Business**                               |
-|--------------------------------------------------|:------:|----------------------------------------------------|
+| ------------------------------------------------ | :----: | -------------------------------------------------- |
 | **Navigate complex interfaces** during incidents |        | **Get instant analysis** with natural language     |
 | **Build dashboards** during incidents            | **VS** | **Automatic dashboards** with zero configuration   |
 | **Manually correlate data** across systems       |        | **AI-powered correlation** and root cause analysis |
@@ -272,7 +272,7 @@ Experience the future of infrastructure monitoring with AI that actually works.
 **AI Features Overview:**
 
 | **Capability**           | **What It Does**                    | **Access**                           |
-|--------------------------|-------------------------------------|--------------------------------------|
+| ------------------------ | ----------------------------------- | ------------------------------------ |
 | **AI Chat with Netdata** | Ask questions in natural language   | Available now for all deployments    |
 | **AI DevOps Copilot**    | CLI-based AI automation             | Available now with MCP tools         |
 | **AI Insights**          | Professional reports in 2-3 minutes | Business plans get unlimited reports |

docs/Netdata Cloud/Unclaim and Reclaim a Node.mdx

@@ -15,7 +15,7 @@ slug: "/netdata-cloud/unclaim-and-reclaim-a-node"
 **What's the difference between unclaiming/reclaiming and removing a node?**
 
 | Action                | What it does                                          | Agent status                            |
-|-----------------------|-------------------------------------------------------|-----------------------------------------|
+| --------------------- | ----------------------------------------------------- | --------------------------------------- |
 | **Unclaim & Reclaim** | Disconnect from current Space, connect to a new Space | Agent keeps running                     |
 | **Remove**            | Permanently delete node from Netdata Cloud            | Agent may keep running but disconnected |
 
@@ -75,7 +75,7 @@ sudo systemctl restart netdata
 Run the standard claim command with your new Space's token:
 
 ```bash
-bash <(curl -Ss https://my-netdata.io/kickstart.sh) --claim-token YOUR_NEW_TOKEN --claim-rooms YOUR_ROOMS --claim-url https://app.netdata.cloud
+bash <(curl -Ss https://get.netdata.cloud/kickstart.sh) --claim-token YOUR_NEW_TOKEN --claim-rooms YOUR_ROOMS --claim-url https://app.netdata.cloud
 ```
 
 ### Option 2: Configuration File
@@ -119,9 +119,9 @@ After reclaiming, verify the node appears in:
 - Verify the claim token is correct for the new Space
 - Check `/var/lib/netdata/cloud.d/` was removed before reclaiming
 - Review agent logs using:
-    - `journalctl --namespace netdata -b 0 | grep -i CLAIM`
-    - or:
-    - `grep -i CLAIM /var/log/netdata/daemon.log`
+  - `journalctl --namespace netdata -b 0 | grep -i CLAIM`
+  - or:
+  - `grep -i CLAIM /var/log/netdata/daemon.log`
 
 **Reconnection fails:**