aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJPR2019-05-24 04:42:38 +0200
committerJPR2019-05-24 04:42:38 +0200
commitbe40007de49140d403bb1dad1af9f4f1e3fe5003 (patch)
tree09aa8d5eafaca49027aec020748edadaf622429f
parentab2ce9241e989ac899e4d43333b527e124c0c749 (diff)
Fixing typos
-rw-r--r--proofs/refiner.ml2
-rw-r--r--tactics/abstract.ml2
-rw-r--r--tactics/tacticals.ml2
3 files changed, 3 insertions, 3 deletions
diff --git a/proofs/refiner.ml b/proofs/refiner.ml
index 6476e298e6..799f4a380b 100644
--- a/proofs/refiner.ml
+++ b/proofs/refiner.ml
@@ -289,7 +289,7 @@ let tclIFTHENTRYELSEMUST tac1 tac2 gl =
(* Fails if a tactic did not solve the goal *)
let tclCOMPLETE tac = tclTHEN tac (tclFAIL_s "Proof is not complete.")
-(* Try the first that's solves the current goal *)
+(* Try the first that solves the current goal *)
let tclSOLVE tacl = tclFIRST (List.map tclCOMPLETE tacl)
diff --git a/tactics/abstract.ml b/tactics/abstract.ml
index 71d71cd3ca..a5b2f99457 100644
--- a/tactics/abstract.ml
+++ b/tactics/abstract.ml
@@ -99,7 +99,7 @@ let cache_term_by_tactic_then ~opaque ~name_op ?(goal_type=None) tac tacK =
(* This is important: The [Global] and [Proof Theorem] parts of the
goal_kind are not relevant here as build_constant_by_tactic does
use the noop terminator; but beware if some day we remove the
- redundancy on constraint declaration. This opens up an interesting
+ redundancy on constant declaration. This opens up an interesting
question, how does abstract behave when discharge is local for example?
*)
let goal_kind, suffix = if opaque
diff --git a/tactics/tacticals.ml b/tactics/tacticals.ml
index 2467671d38..59fd8b37d6 100644
--- a/tactics/tacticals.ml
+++ b/tactics/tacticals.ml
@@ -481,7 +481,7 @@ module New = struct
) <*>
tclUNIT res
- (* Try the first that's solves the current goal *)
+ (* Try the first that solves the current goal *)
let tclSOLVE tacl = tclFIRST (List.map tclCOMPLETE tacl)
let tclPROGRESS t =