From f4a230b627bf9ff53e14719609849ee05b022480 Mon Sep 17 00:00:00 2001
From: Carl Dong <accounts@carldong.me>
Date: Thu, 11 Apr 2019 12:54:20 -0400
Subject: [PATCH] docs: Clarify PR guidelines w/re documentation

---
 CONTRIBUTING.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 007ebd7ccf..5df99adba8 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -220,6 +220,7 @@ In general, all pull requests must:
   - Not break the existing test suite;
   - Where bugs are fixed, where possible, there should be unit tests
     demonstrating the bug and also proving the fix. This helps prevent regression.
+  - Change relevant comments and documentation when behaviour of code changes.
 
 Patches that change Bitcoin consensus rules are considerably more involved than
 normal because they affect the entire ecosystem and so must be preceded by