diff options
author | hugovalente-pm <hugo@netdata.cloud> | 2023-01-31 17:40:20 +0000 |
---|---|---|
committer | hugovalente-pm <hugo@netdata.cloud> | 2023-01-31 17:40:20 +0000 |
commit | a9b93129572b92578947a676b503e9d410219773 (patch) | |
tree | 3e3bb723f804858b0396e9f03a7abc52cb60fdeb | |
parent | 8e57cd9ec774eb3e1e64c7bfec1fbdcc65564329 (diff) |
fixed some gramatical errors.events-docs
-rw-r--r-- | docs/cloud/insights/events-feed.md | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/cloud/insights/events-feed.md b/docs/cloud/insights/events-feed.md index 3570ef053f..6f7cfa58b1 100644 --- a/docs/cloud/insights/events-feed.md +++ b/docs/cloud/insights/events-feed.md @@ -9,12 +9,12 @@ learn_rel_path: "Concepts" learn_docs_purpose: "Present the Netdata Events feed." --> -Netdata Cloud provides the Events feed which is a powerful feature that keeps track of events that happen both on our infrastructure and on your Space. -You will be able to use it to investigate events that occurred in that past and can be key on your troubleshooting task. +Netdata Cloud provides the Events feed which is a powerful feature that keeps track of events that happen both on your infrastructure and in your Space. +You will be able to use it to investigate events that occurred in the past and can be key to your troubleshooting task. #### What are the available events? -At an high-level view, these are the domains from which the Events feed will provide visibility into. +At a high-level view, these are the domains from which the Events feed will provide visibility into. > ⚠️ Based on your space's plan different allowances are defined to query past data. @@ -33,8 +33,8 @@ At an high-level view, these are the domains from which the Events feed will pro | Node Become Offline | The node is offline, not streaming metrics to Cloud and not available in any parent node.| TO-DO | | Node Created | The node is created but it is still Unseen on Cloud, didn't establish a successful connection yet.| TO-DO | | Node Removed | The node was removed from the Space through the `Delete` action, if it becomes Live again it will be automatically added. | TO-DO | -| Node Restored | The node is restored, if node become Live after a remove action it re-added to the Space. | TO-DO | -| Node Deleted | The node is deleted from the Space, see this as an hard delete and won't be re-added to the Space if it becomes live. | TO-DO | +| Node Restored | The node is restored, if node becomes Live after a remove action it is re-added to the Space. | TO-DO | +| Node Deleted | The node is deleted from the Space, see this as a hard delete and won't be re-added to the Space if it becomes live. | TO-DO | TO-DO: Agent events? @@ -42,7 +42,7 @@ TO-DO: Agent events? | **Event name** | **Description** | **Example** | | :-- | :-- | :-- | -| Node Alert State Changed | These are node alert state transition events and can be seen as an alert history log. You will be able to transitions to or from any of these states: Cleared, Warning, Critical, Removed, Error or Unknown | TO-DO | +| Node Alert State Changed | These are node alert state transition events and can be seen as an alert history log. You will be able to see transitions to or from any of these states: Cleared, Warning, Critical, Removed, Error or Unknown | TO-DO | #### Who can access the events? |