examples: Trim .txt files trailing whitespace

via OSX: find . -name '*.txt' -exec sed -i '' -E 's/[[:space:]]+$//' {} +

examples/cross_calculator/lazarus/readme.txt

@@ -1,8 +1,8 @@
-This example demonstrates how to use Nim with Lazarus. The GUI is generated
-with Lazarus, while the "backend" is written in Nim. To compile the example,
-use this command:
-
-  nim c --app:gui --no_main --no_linking backend.nim
-
-Open the ``nimlaz.lpi`` file in Lazarus and run the program.
-
+This example demonstrates how to use Nim with Lazarus. The GUI is generated
+with Lazarus, while the "backend" is written in Nim. To compile the example,
+use this command:
+
+  nim c --app:gui --no_main --no_linking backend.nim
+
+Open the ``nimlaz.lpi`` file in Lazarus and run the program.
+

examples/cross_calculator/readme.txt

@@ -1,13 +1,13 @@
-The cross platform calculator illustrates how to use Nim to create a backend
-called by different native user interfaces.
-
-Since the purpose of the example is to show how the cross platform code
-interacts with Nimrod the actual backend code is just a simple addition proc.
-By keeping your program logic in Nim you can easily reuse it in different
-platforms.
-
-To avoid duplication of code, the backend code lies in a separate directory and
-each platform compiles it with a different custom build process, usually
-generating C code in a temporary build directory.
-
-For a more elaborate and useful example see the cross_todo example.
+The cross platform calculator illustrates how to use Nim to create a backend
+called by different native user interfaces.
+
+Since the purpose of the example is to show how the cross platform code
+interacts with Nimrod the actual backend code is just a simple addition proc.
+By keeping your program logic in Nim you can easily reuse it in different
+platforms.
+
+To avoid duplication of code, the backend code lies in a separate directory and
+each platform compiles it with a different custom build process, usually
+generating C code in a temporary build directory.
+
+For a more elaborate and useful example see the cross_todo example.