aboutsummaryrefslogtreecommitdiff
path: root/dev/doc/proof-engine.md
diff options
context:
space:
mode:
authorJPR2019-05-21 23:07:55 +0200
committerJPR2019-05-21 23:07:55 +0200
commite6322e23958a937fa01960f8ce320717b9863253 (patch)
tree79e2a8c8e7c953c44b3880fa683d82f2a6e6cc85 /dev/doc/proof-engine.md
parente9a5fe993ba36e22316ac9f6ef0564f38a3eb4f9 (diff)
Fixing typos - Part 1
Diffstat (limited to 'dev/doc/proof-engine.md')
-rw-r--r--dev/doc/proof-engine.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/dev/doc/proof-engine.md b/dev/doc/proof-engine.md
index 774552237a..a2c8d2f5ac 100644
--- a/dev/doc/proof-engine.md
+++ b/dev/doc/proof-engine.md
@@ -121,7 +121,7 @@ a limited set of derivation rules), it is recommended to generate proofs as
much as possible by refining in ML tactics when it is possible and easy enough.
Indeed, this prevents dependence on fragile constructions such as unification.
-Obviously, it does not forbid the use of tacticals to mimick what one would do
+Obviously, it does not forbid the use of tacticals to mimic what one would do
in Ltac. Each Ltac primitive has a corresponding ML counterpart with simple
semantics. A list of such tacticals can be found in the `Tacticals` module. Most
of them are a porting of the tacticals from the old engine to the new one, so