Release 2024-09-15

README.markdown

@@ -15,9 +15,9 @@ Mindcode focuses of the following priorities:
 * Employing various [optimizations](doc/syntax/SYNTAX-6-OPTIMIZATIONS.markdown) to produce efficient code. 
 
 > [!NOTE]
-> Please have a look at planned upcoming changes to Mindcode
-> [here](https://github.com/cardillan/mindcode/discussions/142). The changes will be substantial, and any comments 
-> and suggestions are welcome now while the changes are still being discussed.
+> Please have a look at planned [upcoming changes to Mindcode](https://github.com/cardillan/mindcode/discussions/142).
+> These changes will be substantial, and any comments and suggestions are welcome now while the changes are still 
+> being deliberated.
 
 **Schemacode** is a specialized definition language designed for creating a complete Mindustry schematic as a text 
 file. [Schematics builder](doc/syntax/SCHEMACODE.markdown) can be used to turn these definition files directly into 

doc/syntax/SYNTAX-5-OTHER.markdown

@@ -35,7 +35,7 @@ of the `remarks` option are:
 * `none`: remarks are suppressed in the compiled code - they do not appear there at all.
 * `passive`: remarks are included in the compiled code, but a jump is generated in front each block of continuous 
   remarks, so that the print statement themselves aren't executed. This is the default value.
-* `active`: remarks are included in the compiled code can be executed, producing actual output to the text buffer.
+* `active`: remarks are included in the compiled code and are executed, producing actual output to the text buffer.
 
 Passive remarks can be used for putting instructions or comments in the compiled code, or to mark a specific portion 
 of the code. Remarks in a loop may help identifying individual iterations when the loop is unrolled, for example.

doc/syntax/SYNTAX-6-OPTIMIZATIONS.markdown

@@ -1378,15 +1378,15 @@ into Mindustry processors even if they're longer than what the Mindustry GUI all
 
 ### Remarks
 
-The print merging optimization will also merge print instructions generated by the `remark()` function. Instructions 
-generated by remarks are merged differently to normal print instructions:
+The print merging optimization will also merge `print` instructions generated by the `remark()` function. Instructions 
+generated by remarks are merged differently to standard `print` instructions:
 
 * `print` instructions generated from different `remark()` function calls are never merged. Only instructions 
   generated from a single `remark()` are merged together.
 * All constant values are merged together regardless of the resulting string length, even on the `basic` 
   optimization level.
 
-If the print merging optimization is not active, instructions from `remark()` function aren't merged.
+If the print merging optimization is not active, instructions from `remark()` functions aren't merged.
 
 # Optimization for speed
 

webapp/src/main/resources/templates/common.ftlh

@@ -42,7 +42,7 @@
 <#macro footer>
 <footer class="mt-8 text-xs text-center border border-t-2 border-l-0 border-r-0 border-b-0 border-gray-700">
     <div class="mt-4 flex justify-between">
-        <div><strong>2024-09-10</strong></div>
+        <div><strong>2024-09-15</strong></div>
         <div><strong>PRIVACY POLICY</strong>: This website does not track its users. The Mindcode and schematics you submit for compilation is kept for later analysis.
             No other information is kept about you or your actions on the site.</div>
         <div>Created by François (<a class="underline text-blue-500" href="https://github.com/francois">GitHub</a>,