Small documentation tweaks

Author: tfry-git

README.md

@@ -8,7 +8,7 @@ microcontroller with Arduino support).
 - For an overview, getting started, troubleshooting basic problem: **Continue reading on this page**
 - More usage examples: The regular [examples folder](/examples)
 - All functions / classes: [full API reference](https://tfry-git.github.io/EmbAJAX/api/annotated.html)
-- Tweaking RAM, flash, and network usage, understanding internal workings: [Library design considerations](/docs/Technical.md)
+- Tweaking RAM, flash, and network usage, understanding internal workings: [Technical details](/docs/Technical.md)
 
 ## Overview
 

docs/Technical.md

@@ -1,4 +1,18 @@
-# Technical background / tweaking performance and resource usage
+# Technical details and performance tweaks
+
+## RAM vs. Flash
+
+On some MCU-architectures, RAM and FLASH reside in two logically distinct address spaces. This implies that regular const char* strings
+need to be copied into RAM address space, even if they are fully static. EmbAJAX needs many string constants, and is therefore quite affected
+by this problem.
+
+The Arduino F() macro helps to work around this (further reading, there), but does incur a small performance (and code size) penalty, which can
+be avoided if a) RAM usage is not an issue, or b) the MCU uses a unified address space.
+
+By default, EmbAJAX tries to detect case b), and will disable use of F() strings, then. The USE_PROGMEM_STRINGS define near the top of EmbAJAX.h
+allows you to tweak this for special needs.
+
+Note that at the time of this writing, there is no distinct support for keeping ```EmbAJAXStatic``` blocks in PROGMEM. Pull requests are welcome.
 
 ## Latency vs. network traffic vs. performance
 
@@ -37,20 +51,6 @@ To avoid sending all states of all controls on each request from each client, th
 sent to any client. The client pings back its current revision number on each request, so only real changes have to be forwarded. This is particularly
 important where several clients are accessing the same page, and need to be kept in sync.
 
-## RAM vs. Flash
-
-On some MCU-architectures, RAM and FLASH reside in two logically distinct address spaces. This implies that regular const char* strings
-need to be copied into RAM address space, even if they are fully static. EmbAJAX needs many string constants, and is therefore quite affected
-by this problem.
-
-The Arduino F() macro helps to work around this (further reading, there), but does incur a small performance (and code size) penalty, which can
-be avoided if a) RAM usage is not an issue, or b) the MCU uses a unified address space.
-
-By default, EmbAJAX tries to detect case b), and will disable use of F() strings, then. The USE_PROGMEM_STRINGS define near the top of EmbAJAX.h
-allows you to tweak this for special needs.
-
-Note that at the time of this writing, there is no distinct support for keeping ```EmbAJAXStatic``` blocks in PROGMEM. Pull requests are welcome.
-
 ## Some further implementation notes
 
 Concurrent access by an arbitrary number of separate clients is the main reason behind going with AJAX, instead of WebSockets, even if the