aboutsummaryrefslogtreecommitdiff
path: root/dev
diff options
context:
space:
mode:
authorcoqbot-app[bot]2020-10-27 21:12:37 +0000
committerGitHub2020-10-27 21:12:37 +0000
commitc8110e13cceab22dd855de7ee2114bcb4eedd699 (patch)
tree9fa2c8f1922075942998828523137debf9bf0c1e /dev
parent96354508a50f12a2af49bd95073c6a24cea69713 (diff)
parent480d34fc22c195d4b19f639345fa993652838894 (diff)
Merge PR #13219: Rename mlg grammar nonterminals to make documented and mlg grammars more consistent
Reviewed-by: Zimmi48 Reviewed-by: herbelin Ack-by: SkySkimmer
Diffstat (limited to 'dev')
-rw-r--r--dev/doc/parsing.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/dev/doc/parsing.md b/dev/doc/parsing.md
index 4982e3e94d..4956b91d01 100644
--- a/dev/doc/parsing.md
+++ b/dev/doc/parsing.md
@@ -210,7 +210,7 @@ command. The first square bracket around a nonterminal definition is for groupi
level definitions, which are separated with `|`, for example:
```
- tactic_expr:
+ ltac_expr:
[ "5" RIGHTA
[ te = binder_tactic -> { te } ]
| "4" LEFTA
@@ -220,8 +220,8 @@ level definitions, which are separated with `|`, for example:
Grammar extensions can specify what level they are modifying, for example:
```
- tactic_expr: LEVEL "1" [ RIGHTA
- [ tac = tactic_expr; intros = ssrintros_ne -> { tclintros_expr ~loc tac intros }
+ ltac_expr: LEVEL "1" [ RIGHTA
+ [ tac = ltac_expr; intros = ssrintros_ne -> { tclintros_expr ~loc tac intros }
] ];
```