summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorgear0 <misc0815@mailbox.org>2019-05-05 12:09:31 +0200
committergear0 <misc0815@mailbox.org>2019-05-05 12:09:31 +0200
commit92720b92a4fad8193baac0be9fa4dccbc596fb30 (patch)
tree5c9cb323389d3f67f4b38f4b170433c9406f97a7 /doc
parentc628e11c01c3c8c642c540a94ea927be42d6d2f3 (diff)
corrected some minor typos in reference manual
Diffstat (limited to 'doc')
-rw-r--r--doc/gf-refman.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/gf-refman.md b/doc/gf-refman.md
index 3ae3eb866..2a53041d9 100644
--- a/doc/gf-refman.md
+++ b/doc/gf-refman.md
@@ -72,7 +72,7 @@ concrete syntax. Tree formation in abstract syntax, however, is fully
recursive.
Even though run-time GF grammars manipulate just nested tuples, at
-compile time these are represented by by the more fine-grained labelled
+compile time these are represented by the more fine-grained labelled
records and finite functions over algebraic datatypes. This enables the
programmer to write on a higher abstraction level, and also adds type
distinctions and hence raises the level of checking of programs.
@@ -99,7 +99,7 @@ module looks as follows:
}
Here are two concrete syntax modules, one intended for mapping the trees
-to English, the other to Swedish. The mappling is defined by `lincat`
+to English, the other to Swedish. The mapping is defined by `lincat`
definitions assigning a **linearization type** to each category, and
`lin` definitions assigning a **linearization** to each function.
@@ -2515,7 +2515,7 @@ The reserved words used in GF are the following:
- `transfer`
- `variants`
- `where`
-- `with`
+- `with`
The symbols used in GF are the following: