diff options
| author | Guillaume Melquiond | 2015-12-07 10:52:14 +0100 |
|---|---|---|
| committer | Guillaume Melquiond | 2015-12-07 10:52:24 +0100 |
| commit | df3a49a18c5b01984000df9244ecea9c275b30cd (patch) | |
| tree | d14afdb5de5f93e4301f8eba8bddecd5a6597f9a /doc/refman/Program.tex | |
| parent | fe2776f9e0d355cccb0841495a9843351d340066 (diff) | |
Fix some typos.
Diffstat (limited to 'doc/refman/Program.tex')
| -rw-r--r-- | doc/refman/Program.tex | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/refman/Program.tex b/doc/refman/Program.tex index 8e078e9814..3a99bfdd4f 100644 --- a/doc/refman/Program.tex +++ b/doc/refman/Program.tex @@ -201,7 +201,7 @@ in their context. In this case, the obligations should be transparent recursive calls can be checked by the kernel's type-checker. There is an optimization in the generation of obligations which gets rid of the hypothesis corresponding to the -functionnal when it is not necessary, so that the obligation can be +functional when it is not necessary, so that the obligation can be declared opaque (e.g. using {\tt Qed}). However, as soon as it appears in the context, the proof of the obligation is \emph{required} to be declared transparent. @@ -216,7 +216,7 @@ properties. It will generate obligations, try to solve them automatically and fail if some unsolved obligations remain. In this case, one can first define the lemma's statement using {\tt Program Definition} and use it as the goal afterwards. -Otherwise the proof will be started with the elobarted version as a goal. +Otherwise the proof will be started with the elaborated version as a goal. The {\tt Program} prefix can similarly be used as a prefix for {\tt Variable}, {\tt Hypothesis}, {\tt Axiom} etc... |
