summary refs log tree commit diff stats
path: root/doc/idetools.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/idetools.txt
parentc95f6f117a665bc6d3d64ae8703459759973f63f (diff)
downloadNim-657dca5c3b26a088ac291e06308d44d5e52c162f.tar.gz
Fix typos
Diffstat (limited to 'doc/idetools.txt')
-rw-r--r--doc/idetools.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/idetools.txt b/doc/idetools.txt
index 81de9598c..2ffe46d4b 100644
--- a/doc/idetools.txt
+++ b/doc/idetools.txt
@@ -163,7 +163,7 @@ running/debugged user project.
 Compiler as a service (CAAS)
 ============================
 
-The ocasional use of idetools is acceptable for things like
+The occasional use of idetools is acceptable for things like
 definitions, where the user puts the cursor on a symbol or double
 clicks it and after a second or two the IDE displays where that
 symbol is defined. Such latencies would be terrible for features
@@ -533,10 +533,10 @@ run it manually. First you have to compile the tester::
 Running the ``caasdriver`` without parameters will attempt to process
 all the test cases in all three operation modes. If a test succeeds
 nothing will be printed and the process will exit with zero. If any
-test fails, the specific line of the test preceeding the failure
+test fails, the specific line of the test preceding the failure
 and the failure itself will be dumped to stdout, along with a final
 indicator of the success state and operation mode. You can pass the
-parameter ``verbose`` to force all output even on successfull tests.
+parameter ``verbose`` to force all output even on successful tests.
 
 The normal operation mode is called ``ProcRun`` and it involves
 starting a process for each command or query, similar to running