updated for version 7.1a
diff --git a/runtime/doc/if_tcl.txt b/runtime/doc/if_tcl.txt
index b3c81b8..4ab5237 100644
--- a/runtime/doc/if_tcl.txt
+++ b/runtime/doc/if_tcl.txt
@@ -1,4 +1,4 @@
-*if_tcl.txt* For Vim version 7.0. Last change: 2006 Mar 06
+*if_tcl.txt* For Vim version 7.1a. Last change: 2006 Mar 06
VIM REFERENCE MANUAL by Ingo Wilken
diff --git a/runtime/doc/usr_21.txt b/runtime/doc/usr_21.txt
index 53228cc..0b5298e 100644
--- a/runtime/doc/usr_21.txt
+++ b/runtime/doc/usr_21.txt
@@ -1,4 +1,4 @@
-*usr_21.txt* For Vim version 7.0. Last change: 2006 Apr 25
+*usr_21.txt* For Vim version 7.1a. Last change: 2007 May 01
VIM USER MANUAL - by Bram Moolenaar
@@ -421,7 +421,8 @@
:set modelines=10
The 'modeline' option can be used to switch this off. Do this when you are
-working as root or don't trust the files you are editing: >
+working as root on Unix or Administrator on MS-Windows, or when you don't
+trust the files you are editing: >
:set nomodeline
@@ -432,9 +433,9 @@
The "any-text" indicates that you can put any text before and after the part
that Vim will use. This allows making it look like a comment, like what was
done above with /* and */.
- The " vim:" part is what makes Vim recognize this line. The must be white
-space before "vim", or "vim" must be at the start of the line. Thus using
-something like "gvim:" will not work.
+ The " vim:" part is what makes Vim recognize this line. There must be
+white space before "vim", or "vim" must be at the start of the line. Thus
+using something like "gvim:" will not work.
The part between the colons is a ":set" command. It works the same way as
typing the ":set" command, except that you need to insert a backslash before a
colon (otherwise it would be seen as the end of the modeline).
diff --git a/runtime/doc/usr_24.txt b/runtime/doc/usr_24.txt
index 9a961ef..1c15ca5 100644
--- a/runtime/doc/usr_24.txt
+++ b/runtime/doc/usr_24.txt
@@ -1,4 +1,4 @@
-*usr_24.txt* For Vim version 7.0. Last change: 2006 Apr 24
+*usr_24.txt* For Vim version 7.1a. Last change: 2006 Jul 23
VIM USER MANUAL - by Bram Moolenaar
@@ -252,11 +252,18 @@
quite different from using CTRL-P, which would complete any word, while only
members of "struct foo" are valid here.
-For Omni completion to work you may need to do some setup. For C code you
-need to create a tags file and set the 'tags' option. That is explained
-|ft-c-omni|. For other filetypes you may need to do something similar, look
-below |compl-omni-filetypes|. It only works for specific filetypes. Check
-the value of the 'omnifunc' option to find out if it would work.
+For Omni completion to work you may need to do some setup. At least make sure
+filetype plugins are enabled. Your vimrc file should contain a line like
+this: >
+ filetype plugin on
+Or: >
+ filetype plugin indent on
+
+For C code you need to create a tags file and set the 'tags' option. That is
+explained |ft-c-omni|. For other filetypes you may need to do something
+similar, look below |compl-omni-filetypes|. It only works for specific
+filetypes. Check the value of the 'omnifunc' option to find out if it would
+work.
==============================================================================
*24.4* Repeating an insert