From 34dbc5699e8cb36e26bad5a57edc972b82f26c5f Mon Sep 17 00:00:00 2001 From: Nindaleth Date: Wed, 30 Oct 2019 09:08:45 +0100 Subject: fix several typos in documentation and comments (#12553) --- lib/packages/docutils/rst.nim | 2 +- lib/packages/docutils/rstgen.nim | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) (limited to 'lib/packages') 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 = ## `_ 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 -- cgit 1.4.1-2-gfad0