From faf6afd99df457c5298d1867b84d448bd18b5a23 Mon Sep 17 00:00:00 2001
From: MarcoFalke <*~=`'#}+{/-|&$^_@721217.xyz>
Date: Fri, 15 May 2026 16:14:34 +0200
Subject: [PATCH] doc: Move mutex and thread section into guideline section

Previously, they have been in the "Tips and tricks" section, which seems a bit off.
---
 doc/developer-notes.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/doc/developer-notes.md b/doc/developer-notes.md
index 94b33632e65..4a4841cbfcc 100644
--- a/doc/developer-notes.md
+++ b/doc/developer-notes.md
@@ -671,6 +671,11 @@ Additional resources:
  * [GCC Instrumentation Options](https://gcc.gnu.org/onlinedocs/gcc/Instrumentation-Options.html)
  * [Google Sanitizers Wiki](https://github.com/google/sanitizers/wiki)
 
+# Development guidelines
+
+A few non-style-related recommendations for developers, as well as points to
+pay attention to for reviewers of Bitcoin Core code.
+
 ## Locking/mutex usage notes
 
 The code is multi-threaded and uses mutexes and the
@@ -740,11 +745,6 @@ and its `cs_KeyStore` lock for example).
   - [ThreadI2PAcceptIncoming (`b-i2paccept`)](https://doxygen.bitcoincore.org/class_c_connman.html#a57787b4f9ac847d24065fbb0dd6e70f8)
     : Listens for and accepts incoming I2P connections through the I2P SAM proxy.
 
-# Development guidelines
-
-A few non-style-related recommendations for developers, as well as points to
-pay attention to for reviewers of Bitcoin Core code.
-
 ## General Bitcoin Core
 
 - New features should be exposed on RPC first, then can be made available in the GUI.