From 4fef230a1ee1964712e3ac7f325ce00968ac4769 Mon Sep 17 00:00:00 2001
From: Jason Gross
Date: Tue, 12 Aug 2014 11:14:04 -0400
Subject: "allows to", like "allowing to", is improper

It's possible that I should have removed more "allows", as many
instances of "foo allows to bar" could have been replaced by "foo bars"
(e.g., "[Qed] allows to check and save a complete proof term" could be
"[Qed] checks and saves a complete proof term"), but not always (e.g.,
"the optional argument allows to ignore universe polymorphism" should
not be "the optional argument ignores universe polymorphism" but "the
optional argument allows the caller to instruct Coq to ignore universe
polymorphism" or something similar).
---
 kernel/retroknowledge.ml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'kernel/retroknowledge.ml')

diff --git a/kernel/retroknowledge.ml b/kernel/retroknowledge.ml
index 466380f2d6..5a2f5ced78 100644
--- a/kernel/retroknowledge.ml
+++ b/kernel/retroknowledge.ml
@@ -19,7 +19,7 @@ open Term
 (* Type declarations, these types shouldn't be exported they are accessed
    through specific functions. As being mutable and all it is wiser *)
 (* These types are put into two distinct categories: proactive and reactive.
-   Proactive information allows to find the name of a combinator, constructor
+   Proactive information allows finding the name of a combinator, constructor
    or inductive type handling a specific function.
    Reactive information is, on the other hand, everything you need to know
    about a specific name.*)
-- 
cgit v1.2.3