Expunge "allow" + infinitive from source and doc, part 2.

Do the same for "permit", "enable", "prevent", and (where appropriate)
"require".

doc/misc/reftex.texi:
doc/misc/url.texi:
lib/get-permissions.c:
lib/strftime.c:
lisp/org/org-element.el:
lisp/org/org-mobile.el:
lisp/textmodes/reftex-vars.el:
src/bidi.c:
src/emacs.c:
src/xdisp.c:
test/etags/c-src/emacs/src/lisp.h:

Expunge the likes of "This allows to do something" from the above files.

3 files changed, 4 insertions, 4 deletions

diff --git a/src/bidi.c b/src/bidi.c
index 7f5d16b39ed..9b714543dd2 100644
--- a/src/bidi.c
+++ b/src/bidi.c
@@ -3001,7 +3001,7 @@ bidi_resolve_neutral (struct bidi_it *bidi_it)
         {
           /* Arrrgh!!  The UAX#9 algorithm is too deeply entrenched in
              the assumption of batch-style processing; see clauses W4,
-             W5, and especially N1, which require to look far forward
+             W5, and especially N1, which require looking far forward
              (as well as back) in the buffer/string.  May the fleas of
              a thousand camels infest the armpits of those who design
              supposedly general-purpose algorithms by looking at their
diff --git a/src/emacs.c b/src/emacs.c
index 41113f84331..89d8ca784ae 100644
--- a/src/emacs.c
+++ b/src/emacs.c
@@ -2188,7 +2188,7 @@ synchronize_locale (int category, Lisp_Object *plocale, Lisp_Object desired_loca
     {
       *plocale = desired_locale;
 #ifdef WINDOWSNT
-      /* Changing categories like LC_TIME usually requires to specify
+      /* Changing categories like LC_TIME usually requires specifying
          an encoding suitable for the new locale, but MS-Windows's
          'setlocale' will only switch the encoding when LC_ALL is
          specified.  So we ignore CATEGORY, use LC_ALL instead, and
diff --git a/src/xdisp.c b/src/xdisp.c
index 5185e777324..78fddd60fc0 100644
--- a/src/xdisp.c
+++ b/src/xdisp.c
@@ -13139,7 +13139,7 @@ text_outside_line_unchanged_p (struct window *w,
          beginning of a paragraph, before the first strong directional
          character, can change the base direction of the paragraph (unless
          the buffer specifies a fixed paragraph direction), which will
-         require to redisplay the whole paragraph.  It might be worthwhile
+         require redisplaying the whole paragraph.  It might be worthwhile
          to find the paragraph limits and widen the range of redisplayed
          lines to that, but for now just give up this optimization.  */
       if (!NILP (BVAR (XBUFFER (w->contents), bidi_display_reordering))
@@ -18067,7 +18067,7 @@ try_window_id (struct window *w)
      beginning of a paragraph, before the first strong directional
      character, can change the base direction of the paragraph (unless
      the buffer specifies a fixed paragraph direction), which will
-     require to redisplay the whole paragraph.  It might be worthwhile
+     require redisplaying the whole paragraph.  It might be worthwhile
      to find the paragraph limits and widen the range of redisplayed
      lines to that, but for now just give up this optimization and
      redisplay from scratch.  */