Updated documentation

docs/markdown/interfaces.md

@@ -1201,6 +1201,10 @@ These can be used to control various aspects of interface behaviour.
 >   `internal` mode interfaces may still be resolvable by means
 >   of path requests.
 >   
+> * To allow an interface that would *otherwise not* propagate
+>   announces to `internal` mode interfaces to do so, you can
+>   configure the `announces_to_internal` option to `True`.
+>   
 
 ## Interface Modes
 

docs/markdown/understanding.md

@@ -682,6 +682,8 @@ Roaming             ✓     ✕      ✕          ✕           ✓         ✓
 ✓ Will rebroadcast announce
 ✕ Will not rebroadcast announce -->
 
+For a visually intuitive overview of how announce propagation rules function in practice, you can take a look at the [Announce Propagation Simulator](https://rns.moscow/announce-sim.html) hosted by [rns.moscow](https://rns.moscow/).
+
 ### Cryptographic Primitives
 
 Reticulum uses a simple suite of efficient, strong and well-tested cryptographic primitives, with widely available implementations that can be used both on general-purpose CPUs and on microcontrollers.

docs/markdown/using.md

@@ -1175,6 +1175,11 @@ network_identity = ~/.reticulum/storage/identities/my_network
 ...
 ```
 
+For more fine-grained control over how discovered interfaces are auto-connected, additional options are provided for configuraiton. These are not necessary to set in most cases, but can be useful in certain situations.
+
+* The `autoconnect_discovered_mode` options specifies which mode discovered interfaces should be created with when auto-connecting.
+* The `autoconnect_announces_to_internal` option allows you to specify that auto-connected interfaces should propagate announces to `internal` mode interfaces, even if the auto-connected interface’s mode would normally not allow for this.
+
 ## Remote Management
 
 It is possible to allow remote management of Reticulum