Release note: strtab with array chaining, reorder

RELEASES.rst

@@ -632,26 +632,30 @@ Planned
 * Add lightfunc (DUK_TYPE_LIGHTFUNC) primitive type, representing a
   Duktape/C function with a plain tagged value without any heap allocations
 
+* Add duk_push_c_lightfunc() and duk_is_lightfunc() API calls to push user
+  lightfuncs on the value stack and to check if a value is a lightfunc
+
+* Add feature option DUK_OPT_LIGHTFUNC_BUILTINS which causes Duktape to use
+  lightfuncs for almost all built-in functions, saving around 14kB of Duktape
+  heap on 32-bit platforms
+
 * Add multiple feature options to use 16-bit fields and pointer compression
   for reducing memory usage on low memory systems, see doc/low-memory.rst
   for detailed discussion
 
-* Add support for external strings which are like dynamic buffers: a fixed
-  size string header is allocated from the Duktape heap, but the data is
-  behind a pointer
+* Add DUK_OPT_EXTERNAL_STRINGS to enable support for external strings which
+  are like dynamic buffers: a fixed size string header is allocated from the
+  Duktape heap, but the data is behind a pointer
 
-* Add DUK_OPT_EXTERNAL_STRINGS, DUK_OPT_EXTSTR_INTERN_CHECK. and
-  DUK_OPT_EXTSTR_FREE feature options to take advantage of external strings
-  for low memory environments; see doc/low-memory.rst for detailed discussion
+* Add DUK_OPT_EXTSTR_INTERN_CHECK and DUK_OPT_EXTSTR_FREE (used with
+  DUK_OPT_EXTERNAL_STRINGS) to allow string data to be held outside the
+  Duktape heap, which is useful in low memory environments; see
+  doc/low-memory.rst for detailed discussion
 
-* Add duk_push_c_lightfunc() API call to push user lightfuncs on the
-  value stack
-
-* Add duk_is_lightfunc() API call to type check for lightfuncs
-
-* Add feature option DUK_OPT_LIGHTFUNC_BUILTINS which causes Duktape to use
-  lightfuncs for almost all built-in functions, saving around 14kB of Duktape
-  heap on 32-bit platforms
+* Add DUK_OPT_STRTAB_CHAIN and DUK_OPT_STRTAB_CHAIN_SIZE=nnn which enable
+  an alternate string table algorithm intended for low memory environments;
+  the algorithm uses separate chaining with arrays, making allocation
+  behavior easier to handle using a pool allocator, see doc/low-memory.rst
 
 * Add duk_is_error() API call to check if a value inherits from Error