Edits based on feedback

- Added additional "cloud-native" edits
- Reverted some "kill" edits

Author: Lauren

_includes/topnav.html

@@ -28,7 +28,7 @@
 					<a class="mobile-subnav__link" href="https://www.cockroachlabs.com/product/scale/">Scale</a>
 					<a class="mobile-subnav__link" href="https://www.cockroachlabs.com/product/resilience/">Resilience</a>
 					<a class="mobile-subnav__link" href="https://www.cockroachlabs.com/product/geo-distributed">Geo-Partitioning</a>
-					<a class="mobile-subnav__link" href="https://www.cockroachlabs.com/product/cloud-native/">Built for Cloud</a>
+					<a class="mobile-subnav__link" href="https://www.cockroachlabs.com/product/cloud-native/">Cloud Native</a>
 				</div>
 		</div>
 	</div>

_includes/v1.0/faq/clock-synchronization-monitoring.html

@@ -5,4 +5,4 @@
 `clock_offset_meannanos` | The mean difference between the node's clock and other nodes' clocks in nanoseconds
 `clock_offset_stddevnanos` | The standard deviation of the difference between the node's clock and other nodes' clocks in nanoseconds
 
-As described in [the above answer](#what-happens-when-node-clocks-are-not-properly-synchronized), a node will shutdown if the mean offset of its clock from the other nodes' clocks exceeds 80% of the maximum offset allowed. It's recommended to monitor the `clock_offset_meannanos` metric and alert if it's approaching the 80% threshold of your cluster's configured max offset.
+As described in [the above answer](#what-happens-when-node-clocks-are-not-properly-synchronized), a node will shut down if the mean offset of its clock from the other nodes' clocks exceeds 80% of the maximum offset allowed. It's recommended to monitor the `clock_offset_meannanos` metric and alert if it's approaching the 80% threshold of your cluster's configured max offset.

_includes/v1.1/faq/clock-synchronization-monitoring.html

@@ -5,4 +5,4 @@
 `clock_offset_meannanos` | The mean difference between the node's clock and other nodes' clocks in nanoseconds
 `clock_offset_stddevnanos` | The standard deviation of the difference between the node's clock and other nodes' clocks in nanoseconds
 
-As described in [the above answer](#what-happens-when-node-clocks-are-not-properly-synchronized), a node will shutdown if the mean offset of its clock from the other nodes' clocks exceeds 80% of the maximum offset allowed. It's recommended to monitor the `clock_offset_meannanos` metric and alert if it's approaching the 80% threshold of your cluster's configured max offset.
+As described in [the above answer](#what-happens-when-node-clocks-are-not-properly-synchronized), a node will shut down if the mean offset of its clock from the other nodes' clocks exceeds 80% of the maximum offset allowed. It's recommended to monitor the `clock_offset_meannanos` metric and alert if it's approaching the 80% threshold of your cluster's configured max offset.

_includes/v19.1/faq/clock-synchronization-monitoring.html

@@ -5,4 +5,4 @@
 `clock_offset_meannanos` | The mean difference between the node's clock and other nodes' clocks in nanoseconds
 `clock_offset_stddevnanos` | The standard deviation of the difference between the node's clock and other nodes' clocks in nanoseconds
 
-As described in [the above answer](#what-happens-when-node-clocks-are-not-properly-synchronized), a node will shutdown if the mean offset of its clock from the other nodes' clocks exceeds 80% of the maximum offset allowed. It's recommended to monitor the `clock_offset_meannanos` metric and alert if it's approaching the 80% threshold of your cluster's configured max offset.
+As described in [the above answer](#what-happens-when-node-clocks-are-not-properly-synchronized), a node will shut down if the mean offset of its clock from the other nodes' clocks exceeds 80% of the maximum offset allowed. It's recommended to monitor the `clock_offset_meannanos` metric and alert if it's approaching the 80% threshold of your cluster's configured max offset.

_includes/v19.2/faq/clock-synchronization-monitoring.html

@@ -5,4 +5,4 @@
 `clock_offset_meannanos` | The mean difference between the node's clock and other nodes' clocks in nanoseconds
 `clock_offset_stddevnanos` | The standard deviation of the difference between the node's clock and other nodes' clocks in nanoseconds
 
-As described in [the above answer](#what-happens-when-node-clocks-are-not-properly-synchronized), a node will shutdown if the mean offset of its clock from the other nodes' clocks exceeds 80% of the maximum offset allowed. It's recommended to monitor the `clock_offset_meannanos` metric and alert if it's approaching the 80% threshold of your cluster's configured max offset.
+As described in [the above answer](#what-happens-when-node-clocks-are-not-properly-synchronized), a node will shut down if the mean offset of its clock from the other nodes' clocks exceeds 80% of the maximum offset allowed. It's recommended to monitor the `clock_offset_meannanos` metric and alert if it's approaching the 80% threshold of your cluster's configured max offset.

_includes/v2.0/faq/clock-synchronization-monitoring.html

@@ -5,4 +5,4 @@
 `clock_offset_meannanos` | The mean difference between the node's clock and other nodes' clocks in nanoseconds
 `clock_offset_stddevnanos` | The standard deviation of the difference between the node's clock and other nodes' clocks in nanoseconds
 
-As described in [the above answer](#what-happens-when-node-clocks-are-not-properly-synchronized), a node will shutdown if the mean offset of its clock from the other nodes' clocks exceeds 80% of the maximum offset allowed. It's recommended to monitor the `clock_offset_meannanos` metric and alert if it's approaching the 80% threshold of your cluster's configured max offset.
+As described in [the above answer](#what-happens-when-node-clocks-are-not-properly-synchronized), a node will shut down if the mean offset of its clock from the other nodes' clocks exceeds 80% of the maximum offset allowed. It's recommended to monitor the `clock_offset_meannanos` metric and alert if it's approaching the 80% threshold of your cluster's configured max offset.

_includes/v2.1/faq/clock-synchronization-monitoring.html

@@ -5,4 +5,4 @@
 `clock_offset_meannanos` | The mean difference between the node's clock and other nodes' clocks in nanoseconds
 `clock_offset_stddevnanos` | The standard deviation of the difference between the node's clock and other nodes' clocks in nanoseconds
 
-As described in [the above answer](#what-happens-when-node-clocks-are-not-properly-synchronized), a node will shutdown if the mean offset of its clock from the other nodes' clocks exceeds 80% of the maximum offset allowed. It's recommended to monitor the `clock_offset_meannanos` metric and alert if it's approaching the 80% threshold of your cluster's configured max offset.
+As described in [the above answer](#what-happens-when-node-clocks-are-not-properly-synchronized), a node will shut down if the mean offset of its clock from the other nodes' clocks exceeds 80% of the maximum offset allowed. It's recommended to monitor the `clock_offset_meannanos` metric and alert if it's approaching the 80% threshold of your cluster's configured max offset.

_includes/v20.1/faq/clock-synchronization-monitoring.html

@@ -5,4 +5,4 @@
 `clock_offset_meannanos` | The mean difference between the node's clock and other nodes' clocks in nanoseconds
 `clock_offset_stddevnanos` | The standard deviation of the difference between the node's clock and other nodes' clocks in nanoseconds
 
-As described in [the above answer](#what-happens-when-node-clocks-are-not-properly-synchronized), a node will shutdown if the mean offset of its clock from the other nodes' clocks exceeds 80% of the maximum offset allowed. It's recommended to monitor the `clock_offset_meannanos` metric and alert if it's approaching the 80% threshold of your cluster's configured max offset.
+As described in [the above answer](#what-happens-when-node-clocks-are-not-properly-synchronized), a node will shut down if the mean offset of its clock from the other nodes' clocks exceeds 80% of the maximum offset allowed. It's recommended to monitor the `clock_offset_meannanos` metric and alert if it's approaching the 80% threshold of your cluster's configured max offset.

_includes/v20.2/faq/clock-synchronization-monitoring.html

@@ -5,4 +5,4 @@
 `clock_offset_meannanos` | The mean difference between the node's clock and other nodes' clocks in nanoseconds
 `clock_offset_stddevnanos` | The standard deviation of the difference between the node's clock and other nodes' clocks in nanoseconds
 
-As described in [the above answer](#what-happens-when-node-clocks-are-not-properly-synchronized), a node will shutdown if the mean offset of its clock from the other nodes' clocks exceeds 80% of the maximum offset allowed. It's recommended to monitor the `clock_offset_meannanos` metric and alert if it's approaching the 80% threshold of your cluster's configured max offset.
+As described in [the above answer](#what-happens-when-node-clocks-are-not-properly-synchronized), a node will shut down if the mean offset of its clock from the other nodes' clocks exceeds 80% of the maximum offset allowed. It's recommended to monitor the `clock_offset_meannanos` metric and alert if it's approaching the 80% threshold of your cluster's configured max offset.

releases/v1.0.md

@@ -32,7 +32,7 @@ Get future release notes emailed to you:
 
 ### General Availability
 
-With this release, CockroachDB graduates from beta to a production-ready cloud-native database designed to power business at any scale from startup to enterprise. Years of development have gone into the capabilities included, from **distributed SQL** workloads with guaranteed ACID semantics, to **multi-active availability** with consistent consensus-based replication, to **simple and flexible deployment** and operations, to enterprise-scale **distributed, incremental backup and restore**.
+With this release, CockroachDB graduates from beta to a production-ready database built for the cloud and designed to power business at any scale from startup to enterprise. Years of development have gone into the capabilities included, from **distributed SQL** workloads with guaranteed ACID semantics, to **multi-active availability** with consistent consensus-based replication, to **simple and flexible deployment** and operations, to enterprise-scale **distributed, incremental backup and restore**.
 
 Read more about these critical product areas in [this blog post](https://www.cockroachlabs.com/blog/cockroachdb-1-0-release/), and then get started:
 

v1.0/frequently-asked-questions.md

@@ -18,7 +18,7 @@ CockroachDB is well suited for applications that require reliable, available, an
 
 - Distributed or replicated OLTP
 - Multi-datacenter deployments
-- Cloud-native infrastructure initiatives
+- Infrastructure initiatives built for the cloud
 
 ## When is CockroachDB not a good choice?
 

v1.0/stop-a-node.md

@@ -66,7 +66,7 @@ If you need to troubleshoot this command's behavior, you can change its [logging
 
 2. If the node is running in the background and you are using a process manager for automatic restarts, use the process manager to stop the `cockroach` process without restarting it.
 
-    If the node is running in the background and you are not using a process manager, send a stop signal to the `cockroach` process, for example:
+    If the node is running in the background and you are not using a process manager, send a kill signal to the `cockroach` process, for example:
 
     ~~~ shell
     $ pkill cockroach

v1.1/frequently-asked-questions.md

@@ -20,7 +20,7 @@ CockroachDB is well suited for applications that require reliable, available, an
 - Multi-datacenter deployments
 - Multi-region deployments
 - Cloud migrations
-- Cloud-native infrastructure initiatives
+- Infrastructure initiatives built for the cloud
 
 ## When is CockroachDB not a good choice?
 

v1.1/stop-a-node.md

@@ -84,7 +84,7 @@ If you need to troubleshoot this command's behavior, you can change its [logging
 
 2. If the node is running in the background and you are using a process manager for automatic restarts, use the process manager to stop the `cockroach` process without restarting it.
 
-    If the node is running in the background and you are not using a process manager, send a stop signal to the `cockroach` process, for example:
+    If the node is running in the background and you are not using a process manager, send a kill signal to the `cockroach` process, for example:
 
     ~~~ shell
     $ pkill cockroach

v19.1/frequently-asked-questions.md

@@ -28,7 +28,7 @@ CockroachDB is well suited for applications that require reliable, available, an
 - Multi-datacenter deployments
 - Multi-region deployments
 - Cloud migrations
-- Cloud-native infrastructure initiatives
+- Infrastructure initiatives built for the cloud
 
 CockroachDB returns single-row reads in 2ms or less and single-row writes in 4ms or less, and supports a variety of [SQL and operational tuning practices](performance-tuning.html) for optimizing query performance. However, CockroachDB is not yet suitable for heavy analytics / OLAP.
 

v19.1/stop-a-node.md

@@ -80,7 +80,7 @@ If you need to troubleshoot this command's behavior, you can change its [logging
 
 2. If the node is running in the background and you are using a process manager for automatic restarts, use the process manager to stop the `cockroach` process without restarting it.
 
-    If the node is running in the background and you are not using a process manager, send a stop signal to the `cockroach` process, for example:
+    If the node is running in the background and you are not using a process manager, send a kill signal to the `cockroach` process, for example:
 
     {% include copy-clipboard.html %}
     ~~~ shell

v19.2/cockroach-quit.md

@@ -82,7 +82,7 @@ If you need to troubleshoot this command's behavior, you can change its [logging
 
 2. If the node is running in the background and you are using a process manager for automatic restarts, use the process manager to stop the `cockroach` process without restarting it.
 
-    If the node is running in the background and you are not using a process manager, send a stop signal to the `cockroach` process, for example:
+    If the node is running in the background and you are not using a process manager, send a kill signal to the `cockroach` process, for example:
 
     {% include copy-clipboard.html %}
     ~~~ shell

v19.2/frequently-asked-questions.md

@@ -28,7 +28,7 @@ CockroachDB is well suited for applications that require reliable, available, an
 - Multi-datacenter deployments
 - Multi-region deployments
 - Cloud migrations
-- Cloud-native infrastructure initiatives
+- Infrastructure initiatives built for the cloud
 
 CockroachDB returns single-row reads in 2ms or less and single-row writes in 4ms or less, and supports a variety of [SQL and operational tuning practices](performance-tuning.html) for optimizing query performance. However, CockroachDB is not yet suitable for heavy analytics / OLAP.
 

v2.0/frequently-asked-questions.md

@@ -19,7 +19,7 @@ CockroachDB is well suited for applications that require reliable, available, an
 - Multi-datacenter deployments
 - Multi-region deployments
 - Cloud migrations
-- Cloud-native infrastructure initiatives
+- Infrastructure initiatives built for the cloud
 
 CockroachDB returns single-row reads in 2ms or less and single-row writes in 4ms or less, and supports a variety of [SQL and operational tuning practices](performance-tuning.html) for optimizing query performance. However, CockroachDB is not yet suitable for heavy analytics / OLAP.
 

v2.0/stop-a-node.md

@@ -74,7 +74,7 @@ If you need to troubleshoot this command's behavior, you can change its [logging
 
 2. If the node is running in the background and you are using a process manager for automatic restarts, use the process manager to stop the `cockroach` process without restarting it.
 
-    If the node is running in the background and you are not using a process manager, send a stop signal to the `cockroach` process, for example:
+    If the node is running in the background and you are not using a process manager, send a kill signal to the `cockroach` process, for example:
 
     ~~~ shell
     $ pkill cockroach

v2.1/frequently-asked-questions.md

@@ -19,7 +19,7 @@ CockroachDB is well suited for applications that require reliable, available, an
 - Multi-datacenter deployments
 - Multi-region deployments
 - Cloud migrations
-- Cloud-native infrastructure initiatives
+- Infrastructure initiatives built for the cloud
 
 CockroachDB returns single-row reads in 2ms or less and single-row writes in 4ms or less, and supports a variety of [SQL and operational tuning practices](performance-tuning.html) for optimizing query performance. However, CockroachDB is not yet suitable for heavy analytics / OLAP.
 

v20.1/cockroach-quit.md

@@ -87,7 +87,7 @@ If you need to troubleshoot this command's behavior, you can change its [logging
 
 2. If the node is running in the background and you are using a process manager for automatic restarts, use the process manager to stop the `cockroach` process without restarting it.
 
-    If the node is running in the background and you are not using a process manager, send a stop signal to the `cockroach` process, for example:
+    If the node is running in the background and you are not using a process manager, send a kill signal to the `cockroach` process, for example:
 
     {% include copy-clipboard.html %}
     ~~~ shell

v20.1/frequently-asked-questions.md

@@ -28,7 +28,7 @@ CockroachDB is well suited for applications that require reliable, available, an
 - Multi-datacenter deployments
 - Multi-region deployments
 - Cloud migrations
-- Cloud-native infrastructure initiatives
+- Infrastructure initiatives built for the cloud
 
 CockroachDB returns single-row reads in 2ms or less and single-row writes in 4ms or less, and supports a variety of [SQL and operational tuning practices](performance-tuning.html) for optimizing query performance. However, CockroachDB is not yet suitable for heavy analytics / OLAP.
 

v20.2/cluster-setup-troubleshooting.md

@@ -362,7 +362,7 @@ If Go allocated memory is larger than a few hundred megabytes, you might have en
 
 ### Node crashes because of insufficient memory
 
-Often when a node exits without a trace or logging any form of error message, we’ve found that it is the operating system stopping it suddenly due to low memory. So if you're seeing node crashes where the logs just end abruptly, it's probably because the node is running out of memory. On most Unix systems, you can verify if the `cockroach` process was stopped
+Often when a node exits without a trace or logging any form of error message, we’ve found that it is the operating system stopping it suddenly due to low memory. So if you're seeing node crashes where the logs just end abruptly, it's probably because the node is running out of memory. On most Unix systems, you can verify if the `cockroach` process was stopped because the node ran out of memory by running:
 
 ~~~ shell
 $ sudo dmesg | grep -iC 3 "cockroach"

v20.2/cockroach-quit.md

@@ -87,7 +87,7 @@ If you need to troubleshoot this command's behavior, you can change its [logging
 
 2. If the node is running in the background and you are using a process manager for automatic restarts, use the process manager to stop the `cockroach` process without restarting it.
 
-    If the node is running in the background and you are not using a process manager, send a stop signal to the `cockroach` process, for example:
+    If the node is running in the background and you are not using a process manager, send a kill signal to the `cockroach` process, for example:
 
     {% include copy-clipboard.html %}
     ~~~ shell

v20.2/frequently-asked-questions.md

@@ -28,7 +28,7 @@ CockroachDB is well suited for applications that require reliable, available, an
 - Multi-datacenter deployments
 - Multi-region deployments
 - Cloud migrations
-- Cloud-native infrastructure initiatives
+- Iinfrastructure initiatives built for the cloud
 
 CockroachDB returns single-row reads in 2ms or less and single-row writes in 4ms or less, and supports a variety of [SQL and operational tuning practices](performance-tuning.html) for optimizing query performance. However, CockroachDB is not yet suitable for heavy analytics / OLAP.