summary refs log tree commit diff stats
path: root/examples/cross_calculator/readme.txt
diff options
context:
space:
mode:
authorAraq <rumpf_a@web.de>2015-01-28 18:58:05 +0100
committerAraq <rumpf_a@web.de>2015-01-28 19:31:36 +0100
commita4b27622491c9844da2ca15bb8cc3ec36356484e (patch)
tree480313aef9418696a4c2dc2defce8be0da2b1654 /examples/cross_calculator/readme.txt
parentd7023f2be4c9cb93dac91d8e4359c70f52bd5633 (diff)
downloadNim-a4b27622491c9844da2ca15bb8cc3ec36356484e.tar.gz
fixes #325
Diffstat (limited to 'examples/cross_calculator/readme.txt')
-rw-r--r--examples/cross_calculator/readme.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/examples/cross_calculator/readme.txt b/examples/cross_calculator/readme.txt
index 55c403d0e..12ad558d4 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 Nimrod to create a backend

+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 Nimrod you can easily reuse it in different

+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 ellaborate and useful example see the cross_todo example.

+For a more elaborate and useful example see the cross_todo example.