diff --git a/testing/qa/behave/compatibility/resources/features/compatibility/network-management/doorman-certs.feature b/testing/qa/behave/compatibility/resources/features/compatibility/network-management/doorman-certs.feature
index ba0e208d5a..7eb65c9b69 100644
--- a/testing/qa/behave/compatibility/resources/features/compatibility/network-management/doorman-certs.feature
+++ b/testing/qa/behave/compatibility/resources/features/compatibility/network-management/doorman-certs.feature
@@ -46,3 +46,6 @@ Feature: Compatibility - Doorman certificate issuance
       | Corda-Node-Version-X         | Corda-Node-Version-Y  | Doorman-Version-X           | Doorman-Version-Y |
       | R3.CORDA-3.0.0-DEV-PREVIEW-3 | corda-3.0             | doorman-3.0.0-DEV-PREVIEW-3 | doorman-master    |
       | R3.CORDA-3.0.0-DEV-PREVIEW-3 | corda-3.1             | doorman-3.0.0-DEV-PREVIEW-3 | doorman-master    |
+
+  Scenario Outline: Unhappy path scenarios to be added (eg. rejected issuance request). Please also see the OAT Test Suite (https://bitbucket.org/R3-CEV/corda-connect/qa/testing) which covers the CSR process from a functional perspective.
+    Examples: TODO
\ No newline at end of file
diff --git a/testing/qa/behave/compatibility/resources/features/compatibility/network-management/network-parameters.feature b/testing/qa/behave/compatibility/resources/features/compatibility/network-management/network-parameters.feature
index cd6bde8ba0..1d5fc9d72b 100644
--- a/testing/qa/behave/compatibility/resources/features/compatibility/network-management/network-parameters.feature
+++ b/testing/qa/behave/compatibility/resources/features/compatibility/network-management/network-parameters.feature
@@ -30,5 +30,5 @@ Feature: Compatibility - CZ Network Parameters changes
       | Corda-Node-Version           |
       | R3.CORDA-3.0.0-DEV-PREVIEW-3 |
 
-  Scenario Outline: Many more scenarios to be added here (eg. CZ whitelist updates, minimumPlatformVersion, maxMessageSize, maxTransactionSize)
+  Scenario Outline: Many more scenarios to be added here (eg. CZ whitelist updates, minimumPlatformVersion, increase/reduce maxMessageSize, increase/reduce maxTransactionSize)
     Examples: TODO
\ No newline at end of file
diff --git a/testing/qa/behave/compatibility/resources/features/compatibility/node/node-configuration.feature b/testing/qa/behave/compatibility/resources/features/compatibility/node/node-configuration.feature
index b43fdad60c..a91a4a5442 100644
--- a/testing/qa/behave/compatibility/resources/features/compatibility/node/node-configuration.feature
+++ b/testing/qa/behave/compatibility/resources/features/compatibility/node/node-configuration.feature
@@ -1,7 +1,12 @@
 @compatibility @node @configuration
 Feature: Compatibility - Node configuration
   To support an interoperable Corda network, a Corda node must have the ability to transact with another Corda node
-  when configuration changes are applied independently to each node:
+  when configuration changes are applied independently to each node.
+  Configuration changes may be classified into three types:
+  1. Global configuration items that affect all nodes (eg. change of `compatibilityZoneURL` in an R3 network)
+  2. R3 Corda specific configuration items (eg. `relay` configuration, `security` using Apache Shiro)
+  3. General configuration items applicable to both OS and R3 Corda distributions (`database`, identity, addresses for p2p/rpc/web/ssh, jmx configuration, etc)
+  TODO: implementation to provide two modes of operation (spin-up before/after change, spin-up with change-only)
 
   Scenario Outline: Corda (OS) node can transact with another Corda (OS) node where node configuration is changed on one of the Corda OS nodes
     Given a node A of version <Corda-Node-Version-X>