diff --git a/node-compatibity.md b/node-compatibity.md
index e150b9d..2e682d9 100644
@@ -1,23 +1,26 @@
# Cordova and Node.js
-Cordova CLI locally runs on Node.js
-CLI uses specific node versions
+As such, we have some rules and guidelines about Cordova's Node.js usage:
-### Tooling and Platforms
+## Compatibility and Testing
-Include scripts that are run on node, so node versions have to be tested
-Dropping a node version is a major breaking change
+### Tooling (includes CLI) and Platforms
+Cordova CLI, the tooling behind it and Cordova platforms all include scripts that are directly run by Node.js on the developer's machine. As such, we try to make sure those work on the indicate Node.js versions and test these scripts on a senseful collection of Node.js versions (latest supported, major versions, newest).
+When a Node.js version is dropped from this support and testing roster, this manifests a major **breaking change** of said package.
### Plugins and Templates
-Usually only run on the devices, not locally
-CLI does not have to test on all node versions
-Enough to use one Node version, newest and fastest
-Plugin test tooling (paramedic) still has to work for all node versions though :/
+A special case is [`cordova-paramedic`](https://github.com/apache/cordova-paramedic), which is used by all core plugins to run plugin tests. While we control the Node.js version of that and thus could prefer newer Node.js versions, Paramedic can be used by _any_ plugin author to test their plugins as well - and as such has to be tested across multiple Node.js versions and should not drop support for older Node.js versions.
+Example blog post: https://cordova.apache.org/news/2019/04/11/nodejs-6.x-8.x-deprecation-timeline.html