summary refs log tree commit diff stats
path: root/doc
diff options
context:
space:
mode:
authorAdam Weber <agweber@mtu.edu>2020-04-15 23:39:44 -0500
committerGitHub <noreply@github.com>2020-04-16 00:39:44 -0400
commitd72808520b248d72913d8f9e57acdddc95c84465 (patch)
tree72a2336894695565f94d6241432ef80cc881dace /doc
parent60ec5c89c5b54a6f2a249c9c7e525085133da646 (diff)
downloadNim-d72808520b248d72913d8f9e57acdddc95c84465.tar.gz
Grammar correction in backends.rst (#13989)
I hate to be the guy that submits a couple grammatical/spelling corrections.
Diffstat (limited to 'doc')
-rw-r--r--doc/backends.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/backends.rst b/doc/backends.rst
index 7abb786aa..1a6729ee6 100644
--- a/doc/backends.rst
+++ b/doc/backends.rst
@@ -265,7 +265,7 @@ Create a ``maths.c`` file with the following content:
   }
 
 Now you can run the following Unix like commands to first generate C sources
-form the Nim code, then link them into a static binary along your main C
+from the Nim code, then link them into a static binary along your main C
 program::
 
   $ nim c --noMain --noLinking --header:fib.h fib.nim
@@ -276,7 +276,7 @@ generating a ``main()`` function in the generated files, avoid linking the
 object files into a final binary, and explicitly generate a header file for C
 integration. All the generated files are placed into the ``nimcache``
 directory. That's why the next command compiles the ``maths.c`` source plus
-all the ``.c`` files form ``nimcache``. In addition to this path, you also
+all the ``.c`` files from ``nimcache``. In addition to this path, you also
 have to tell the C compiler where to find Nim's ``nimbase.h`` header file.
 
 Instead of depending on the generation of the individual ``.c`` files you can