aboutsummaryrefslogtreecommitdiff
path: root/doc/sphinx/addendum
diff options
context:
space:
mode:
authorLysxia2019-03-18 08:20:10 -0400
committerLysxia2019-03-18 08:20:10 -0400
commitb64dc640d2af26b1ccf2524c1050c16f57d2be35 (patch)
tree7da398778b22be052482aeba914d72a6662beba7 /doc/sphinx/addendum
parent94f9c0c4b6dd517dc3dca031fbcb9ff455309d19 (diff)
[Manual] Move command Context after Let, and more polishing
- Refine some `@term` into `@type`
Diffstat (limited to 'doc/sphinx/addendum')
-rw-r--r--doc/sphinx/addendum/type-classes.rst8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/sphinx/addendum/type-classes.rst b/doc/sphinx/addendum/type-classes.rst
index 60b346c211..e6a5b3972c 100644
--- a/doc/sphinx/addendum/type-classes.rst
+++ b/doc/sphinx/addendum/type-classes.rst
@@ -146,10 +146,10 @@ database.
Sections and contexts
---------------------
-To ease the parametrization of developments by typeclasses, one can use
-the command :cmd:`Context` to introduce variables into section contexts,
-it works similarly to the :cmd:`Variable` vernacular, except it accepts any
-binding context as argument, so variables can implicit, and
+To ease developments parameterized by many instances, one can use the
+:cmd:`Context` command to introduce these parameters into section contexts,
+it works similarly to the command :cmd:`Variable`, except it accepts any
+binding context as an argument, so variables can be implicit, and
:ref:`implicit-generalization` can be used.
For example: