examples: Trim .txt files trailing whitespace

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

5 files changed, 42 insertions, 42 deletions

diff --git a/examples/cross_calculator/lazarus/readme.txt b/examples/cross_calculator/lazarus/readme.txt
index 2d5048445..c704d53fd 100644
--- a/examples/cross_calculator/lazarus/readme.txt
+++ b/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.
+
diff --git a/examples/cross_calculator/readme.txt b/examples/cross_calculator/readme.txt
index 12ad558d4..5011792b9 100644
--- a/examples/cross_calculator/readme.txt
+++ b/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.
diff --git a/examples/cross_todo/nim_backend/readme.txt b/examples/cross_todo/nim_backend/readme.txt
index 16cb592fc..4b31408e3 100644
--- a/examples/cross_todo/nim_backend/readme.txt
+++ b/examples/cross_todo/nim_backend/readme.txt
@@ -1,14 +1,14 @@
-This directory contains the nim backend code for the todo cross platform

-example.

-

-Unlike the cross platform calculator example, this backend features more code,

-using an sqlite database for storage. Also a basic test module is provided, not

-to be included with the final program but to test the exported functionality.

-The test is not embedded directly in the backend.nim file to avoid being able

-to access internal data types and procs not exported and replicate the

-environment of client code.

-

-In a bigger project with several people you could run `nim doc backend.nim`

-(or use the doc2 command for a whole project) and provide the generated html

-documentation to another programer for her to implement an interface without

-having to look at the source code.

+This directory contains the nim backend code for the todo cross platform
+example.
+
+Unlike the cross platform calculator example, this backend features more code,
+using an sqlite database for storage. Also a basic test module is provided, not
+to be included with the final program but to test the exported functionality.
+The test is not embedded directly in the backend.nim file to avoid being able
+to access internal data types and procs not exported and replicate the
+environment of client code.
+
+In a bigger project with several people you could run `nim doc backend.nim`
+(or use the doc2 command for a whole project) and provide the generated html
+documentation to another programer for her to implement an interface without
+having to look at the source code.
diff --git a/examples/cross_todo/readme.txt b/examples/cross_todo/readme.txt
index dfc21d861..5be01e197 100644
--- a/examples/cross_todo/readme.txt
+++ b/examples/cross_todo/readme.txt
@@ -1,5 +1,5 @@
-The cross platform todo illustrates how to use Nim to create a backend

-called by different native user interfaces.

-

-This example builds on the knowledge learned from the cross_calculator example.

-Check it out first to learn how to set up Nim on different platforms.

+The cross platform todo illustrates how to use Nim to create a backend
+called by different native user interfaces.
+
+This example builds on the knowledge learned from the cross_calculator example.
+Check it out first to learn how to set up Nim on different platforms.
diff --git a/examples/readme.txt b/examples/readme.txt
index 8cfd4f82b..dc3d3fb9b 100644
--- a/examples/readme.txt
+++ b/examples/readme.txt
@@ -1,5 +1,5 @@
-In this directory you will find several examples for how to use the Nimrod 
-library. 
+In this directory you will find several examples for how to use the Nimrod
+library.
 
 Copyright (c) 2004-2012 Andreas Rumpf.
 All rights reserved.