From d8e6d56e25610773a1f27b5275e79c4726ee2634 Mon Sep 17 00:00:00 2001 From: Paul Menzel Date: Wed, 2 Nov 2011 22:43:54 +0100 Subject: [PATCH] vim.txt: Correct some typos This patch includes commit fd67c931 [1]. [1] https://github.com/adityam/filter/commit/fd67c931b44af27f0d1f7b1b5e845a577079e103 --- doc/context/third/vim/vim.txt | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/context/third/vim/vim.txt b/doc/context/third/vim/vim.txt index a7fc912..a5a677f 100644 --- a/doc/context/third/vim/vim.txt +++ b/doc/context/third/vim/vim.txt @@ -4,9 +4,9 @@ The vim module This module highlights code snippets using vim as a syntax highlighter. Such a task may appear pointless at first glance. After all, ConTeXt provides excellent syntax highlighting features for TeX, Metapost, XML, -and a few other langauges. And in MkIV, you can specify the grammer to parse a +and a few other languages. And in MkIV, you can specify the grammar to parse a language, and get syntax highlighting for a new language. But writing such -grammers is difficult. More importantly, why reinvent the wheel? Most +grammars is difficult. More importantly, why reinvent the wheel? Most editors, and many other syntax highlighting programs, already syntax highlight many programming languages. Why not just leverage these external programs to generate syntax highlighting? This module does exactly that. @@ -200,7 +200,7 @@ The default color scheme is `pscolor`. Line numbering --------------- -To eanble line numbering for a particular snippet, use: +To enable line numbering for a particular snippet, use: \start[numbering=yes] ... @@ -314,7 +314,7 @@ indent the TeX code. For example: Although, the source code is easy to read, the output will not be. This is because, unlike regular TeX, `\start` ... `\stop` -environment does not ignore whote space. So, the output is the same as +environment does not ignore white space. So, the output is the same as \startitemize \item A hello world example in C -- 1.7.7.1