summary refs log tree commit diff stats
path: root/lib/packages
diff options
context:
space:
mode:
authorNindaleth <Nindaleth@users.noreply.github.com>2019-10-30 09:08:45 +0100
committerMiran <narimiran@disroot.org>2019-10-30 09:08:45 +0100
commit34dbc5699e8cb36e26bad5a57edc972b82f26c5f (patch)
treede04803327f19ef69b46ca46b4e16a09f77fa6d1 /lib/packages
parent1214960a1bde9b45c76caaff0cdea7d2d753b205 (diff)
downloadNim-34dbc5699e8cb36e26bad5a57edc972b82f26c5f.tar.gz
fix several typos in documentation and comments (#12553)
Diffstat (limited to 'lib/packages')
-rw-r--r--lib/packages/docutils/rst.nim2
-rw-r--r--lib/packages/docutils/rstgen.nim2
2 files changed, 2 insertions, 2 deletions
diff --git a/lib/packages/docutils/rst.nim b/lib/packages/docutils/rst.nim
index 26222d951..eaefc7265 100644
--- a/lib/packages/docutils/rst.nim
+++ b/lib/packages/docutils/rst.nim
@@ -1605,7 +1605,7 @@ proc dirCodeBlock(p: var RstParser, nimExtension = false): PRstNode =
   ## <http://docutils.sourceforge.net/docs/ref/rst/directives.html#code>`_ and
   ## the nim extension ``.. code-block::``. If the block is an extension, we
   ## want the default language syntax highlighting to be Nim, so we create a
-  ## fake internal field to comminicate with the generator. The field is named
+  ## fake internal field to communicate with the generator. The field is named
   ## ``default-language``, which is unlikely to collide with a field specified
   ## by any random rst input file.
   ##
diff --git a/lib/packages/docutils/rstgen.nim b/lib/packages/docutils/rstgen.nim
index f9fd9e32b..abbf99fed 100644
--- a/lib/packages/docutils/rstgen.nim
+++ b/lib/packages/docutils/rstgen.nim
@@ -660,7 +660,7 @@ proc mergeIndexes*(dir: string): string =
   ## As convention this proc will split index files into two categories:
   ## documentation and API. API indices will be all joined together into a
   ## single big sorted index, making the bulk of the final index. This is good
-  ## for API documentation because many symbols are repated in different
+  ## for API documentation because many symbols are repeated in different
   ## modules. On the other hand, documentation indices are essentially table of
   ## contents plus a few special markers. These documents will be rendered in a
   ## separate section which tries to maintain the order and hierarchy of the