summary refs log tree commit diff stats
path: root/doc/backends.txt
diff options
context:
space:
mode:
authorFederico Ceratto <federico.ceratto@gmail.com>2015-02-15 16:20:32 +0000
committerFederico Ceratto <federico.ceratto@gmail.com>2015-02-15 16:20:32 +0000
commit657dca5c3b26a088ac291e06308d44d5e52c162f (patch)
treea3009486a0157d0a5d38bfabff3b041cab3e3779 /doc/backends.txt
parentc95f6f117a665bc6d3d64ae8703459759973f63f (diff)
downloadNim-657dca5c3b26a088ac291e06308d44d5e52c162f.tar.gz
Fix typos
Diffstat (limited to 'doc/backends.txt')
-rw-r--r--doc/backends.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/backends.txt b/doc/backends.txt
index c7b60da26..c7939baec 100644
--- a/doc/backends.txt
+++ b/doc/backends.txt
@@ -225,7 +225,7 @@ The JavaScript target doesn't have any further interfacing considerations
 since it also has garbage collection, but the C targets require you to
 initialize Nim's internals, which is done calling a ``NimMain`` function.
 Also, C code requires you to specify a forward declaration for functions or
-the compiler will asume certain types for the return value and parameters
+the compiler will assume certain types for the return value and parameters
 which will likely make your program crash at runtime.
 
 The Nim compiler can generate a C interface header through the ``--header``
@@ -427,7 +427,7 @@ Custom data types
 -----------------
 
 Just like strings, custom data types that are to be shared between Nim and
-the backend will need careful consideration of who controlls who. If you want
+the backend will need careful consideration of who controls who. If you want
 to hand a Nim reference to C code, you will need to use `GC_ref
 <system.html#GC_ref>`_ to mark the reference as used, so it does not get
 freed. And for the C backend you will need to expose the `GC_unref