summaryrefslogtreecommitdiffstats
path: root/docs/developer-and-contributor-corner
diff options
context:
space:
mode:
authorFotis Voutsas <fotis@netdata.cloud>2024-05-30 14:16:13 +0300
committerGitHub <noreply@github.com>2024-05-30 14:16:13 +0300
commit38baccf80a9f070020930ba90a6b57061099b4d7 (patch)
treebbabd9af1defb9d5c5a20d3cbb49ab7005482afa /docs/developer-and-contributor-corner
parentc50be67a4c79d51422e08f6c2f12ae65e3adb1f6 (diff)
Change "War Room" to "Room" and other docs changes (#17783)
Diffstat (limited to 'docs/developer-and-contributor-corner')
-rw-r--r--docs/developer-and-contributor-corner/collect-unbound-metrics.md2
-rw-r--r--docs/developer-and-contributor-corner/kubernetes-k8s-netdata.md2
-rw-r--r--docs/developer-and-contributor-corner/style-guide.md4
3 files changed, 4 insertions, 4 deletions
diff --git a/docs/developer-and-contributor-corner/collect-unbound-metrics.md b/docs/developer-and-contributor-corner/collect-unbound-metrics.md
index d80e8151a0..0f80395fbc 100644
--- a/docs/developer-and-contributor-corner/collect-unbound-metrics.md
+++ b/docs/developer-and-contributor-corner/collect-unbound-metrics.md
@@ -136,7 +136,7 @@ file](https://github.com/netdata/netdata/blob/master/src/go/collectors/go.d.plug
## What's next?
-Now that you're collecting metrics from your Unbound servers, let us know how it's working for you! There's always room
+Now that you're collecting metrics from your Unbound servers, let us know how it's working for you! There's always Room
for improvement or refinement based on real-world use cases. Feel free to [file an
issue](https://github.com/netdata/netdata/issues/new?assignees=&labels=bug%2Cneeds+triage&template=BUG_REPORT.yml) with your
thoughts.
diff --git a/docs/developer-and-contributor-corner/kubernetes-k8s-netdata.md b/docs/developer-and-contributor-corner/kubernetes-k8s-netdata.md
index 92f4d2f085..11982a5b4c 100644
--- a/docs/developer-and-contributor-corner/kubernetes-k8s-netdata.md
+++ b/docs/developer-and-contributor-corner/kubernetes-k8s-netdata.md
@@ -93,7 +93,7 @@ The Netdata Helm chart deploys and enables everything you need for monitoring Ku
Netdata and connect your cluster's nodes, you're ready to check out the visualizations **with zero configuration**.
To get started, [sign in](https://app.netdata.cloud/sign-in?cloudRoute=/spaces) to your Netdata Cloud account. Head over
-to the War Room you connected your cluster to, if not **General**.
+to the Room you connected your cluster to, if not **General**.
Let's walk through monitoring each layer of a Kubernetes cluster using the Overview as our framework.
diff --git a/docs/developer-and-contributor-corner/style-guide.md b/docs/developer-and-contributor-corner/style-guide.md
index db7ed985ff..94656bd768 100644
--- a/docs/developer-and-contributor-corner/style-guide.md
+++ b/docs/developer-and-contributor-corner/style-guide.md
@@ -450,7 +450,7 @@ The following tables describe the standard spelling, capitalization, and usage o
| Term | Definition |
|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| **claimed node** | A node that you've proved ownership of by completing the [connecting to Cloud process](/src/claim/README.md). The claimed node will then appear in your Space and any War Rooms you added it to. |
+| **claimed node** | A node that you've proved ownership of by completing the [connecting to Cloud process](/src/claim/README.md). The claimed node will then appear in your Space and any Rooms you added it to. |
| **Netdata** | The company behind the open-source Netdata Agent and the Netdata Cloud web application. Never use _netdata_ or _NetData_. <br /><br />In general, focus on the user's goals, actions, and solutions rather than what the company provides. For example, write _Learn more about enabling alert notifications on your preferred platforms_ instead of _Netdata sends alert notifications to your preferred platforms_. |
| **Netdata Agent** | The free and open source [monitoring agent](https://github.com/netdata/netdata) that you can install on all of your distributed systems, whether they're physical, virtual, containerized, ephemeral, and more. The Agent monitors systems running Linux, Docker, Kubernetes, macOS, FreeBSD, and more, and collects metrics from hundreds of popular services and applications. |
| **Netdata Cloud** | The web application hosted at [https://app.netdata.cloud](https://app.netdata.cloud) that helps you monitor an entire infrastructure of distributed systems in real time. <br /><br />Never use _Cloud_ without the preceding _Netdata_ to avoid ambiguity. |
@@ -459,7 +459,7 @@ The following tables describe the standard spelling, capitalization, and usage o
| **Space** | The highest level container within Netdata Cloud for a user to organize their team members and nodes within their infrastructure. A Space likely represents an entire organization or a large team. <br /><br />_Space_ is always capitalized. |
| **unreachable node** | A connected node with a disrupted [Agent-Cloud link](/src/aclk/README.md). Unreachable could mean the node no longer exists or is experiencing network connectivity issues with Cloud. |
| **visited node** | A node which has had its Agent dashboard directly visited by a user. A list of these is maintained on a per-user basis. |
-| **War Room** | A smaller grouping of nodes where users can view key metrics in real-time and monitor the health of many nodes with their alert status. War Rooms can be used to organize nodes in any way that makes sense for your infrastructure, such as by a service, purpose, physical location, and more. <br /><br />_War Room_ is always capitalized. |
+| **Room** | A smaller grouping of nodes where users can view key metrics in real-time and monitor the health of many nodes with their alert status. Rooms can be used to organize nodes in any way that makes sense for your infrastructure, such as by a service, purpose, physical location, and more. <br /><br />_Room_ is always capitalized. |
### Other technical terms