nagios vs sensu updates

website/content/docs/intro/vs/nagios.mdx

@@ -1,16 +1,16 @@
 ---
 layout: docs
-page_title: 'Consul vs. Nagios, Sensu'
-sidebar_title: 'Nagios, Sensu'
+page_title: 'Consul vs. Nagios'
+sidebar_title: 'Nagios'
 description: >-
-  Nagios and Sensu are both tools built for monitoring. They are used to quickly
+  Nagios is a tool built for monitoring. It is used to quickly
   notify operators when an issue occurs.
 ---
 
-# Consul vs. Nagios, Sensu
+# Consul vs. Nagios
 
-Nagios and Sensu are both tools built for monitoring. They are used
-to quickly notify operators when an issue occurs.
+Nagios is a tool built for monitoring. It is used to quickly notify
+operators when an issue occurs.
 
 Nagios uses a group of central servers that are configured to perform
 checks on remote hosts. This design makes it difficult to scale Nagios,
@@ -20,21 +20,14 @@ difficult to use with modern DevOps and configuration management tools,
 as local configurations must be updated when remote servers are added
 or removed.
 
-Sensu has a much more modern design, relying on local agents to run
-checks and pushing results to an AMQP broker. A number of servers
-ingest and handle the result of the health checks from the broker. This model
-is more scalable than Nagios, as it allows for much more horizontal scaling
-and a weaker coupling between the servers and agents. However, the central broker
-has scaling limits and acts as a single point of failure in the system.
-
-Consul provides the same health checking abilities as both Nagios and Sensu,
-is friendly to modern DevOps, and avoids the scaling issues inherent in the
-other systems. Consul runs all checks locally, like Sensu, avoiding placing
-a burden on central servers. The status of checks is maintained by the Consul
-servers, which are fault tolerant and have no single point of failure.
-Lastly, Consul can scale to vastly more checks because it relies on edge-triggered
-updates. This means that an update is only triggered when a check transitions
-from "passing" to "failing" or vice versa.
+Consul provides the same health checking abilities as Nagios,
+is friendly to modern DevOps, and avoids the inherent scaling issues.
+Consul runs all checks locally, avoiding placing a burden on central servers. 
+The status of checks is maintained by the Consul servers, which are fault
+tolerant and have no single point of failure. Lastly, Consul can scale to 
+vastly more checks because it relies on edge-triggered updates. This means 
+that an update is only triggered when a check transitions from "passing"
+to "failing" or vice versa.
 
 In a large fleet, the majority of checks are passing, and even the minority
 that are failing are persistent. By capturing changes only, Consul reduces
@@ -48,4 +41,4 @@ to be in a steady state. However, Consul guards against this as well. The
 integrates a distributed failure detector. This means that if a Consul agent fails,
 the failure will be detected, and thus all checks being run by that node can be
 assumed failed. This failure detector distributes the work among the entire cluster
-while, most importantly, enabling the edge triggered architecture to work.
+while, most importantly, enabling the edge triggered architecture to work.

website/data/docs-navigation.js

@@ -15,7 +15,7 @@ export default [
         content: [
           'zookeeper',
           'chef-puppet',
-          'nagios-sensu',
+          'nagios',
           'skydns',
           'smartstack',
           'serf',

website/redirects.next.js

@@ -256,8 +256,8 @@ module.exports = [
     permanent: true,
   },
   {
-    source: '/intro/vs/nagios-sensu',
-    destination: '/docs/intro/vs/nagios-sensu',
+    source: '/intro/vs/nagios',
+    destination: '/docs/intro/vs/nagios',
     permanent: true,
   },
   {