CLDR-18318 kbd: update spec and EBNF for escaping

- review comments

Co-authored-by: Marc Durdin <[email protected]>

Author: srl295

docs/ldml/tr35-keyboards.md

@@ -2213,8 +2213,9 @@ _Attribute:_ `from` (required)
     However, they are required to be escaped in keyboard transforms, to avoid confusion or problems with characters which are syntax in regular expressions.
 
     Sequences not listed here as **Fixed Character Classes** nor as **Escapes** are disallowed.
-    For example, `\0` (octal escape) and `\1` (backreference) are not allowed.
-    `\a` is not defined as a character class and is also disallowed.
+    For example:
+    * `\0` (octal escape) and `\1` (backreference) are not allowed.
+    * `\a` is not defined as a character class and is also disallowed.
 
 - **Character classes**
 
@@ -2232,7 +2233,7 @@ _Attribute:_ `from` (required)
 
     `{x,y}`
 
-    `x` and `y` are required single digits (`1` to `9`) representing the minimum and maximum number of occurrences.
+    `x` and `y` are required single digits (`0` to `9`) representing the minimum and maximum number of occurrences.
 
     `x` must be ≥ 0, `y` must be ≥ x and ≥ 1. 
 

docs/ldml/tr35.md

@@ -228,7 +228,7 @@ The LDML specification is divided into the following parts:
 
 ## <a name="Introduction" href="#Introduction">Introduction</a>
 
-Not long ago, computer systems were like separate worlds, isolated from one another. The internet and related events have changed all that. A single system can be built of many different compFonents, hardware and software, all needing to work together. Many different technologies have been important in bridging the gaps; in the internationalization arena, Unicode has provided a lingua franca for communicating textual data. However, there remain differences in the locale data used by different systems.
+Not long ago, computer systems were like separate worlds, isolated from one another. The internet and related events have changed all that. A single system can be built of many different components, hardware and software, all needing to work together. Many different technologies have been important in bridging the gaps; in the internationalization arena, Unicode has provided a lingua franca for communicating textual data. However, there remain differences in the locale data used by different systems.
 
 The best practice for internationalization is to store and communicate language-neutral data, and format that data for the client. This formatting can take place on any of a number of the components in a system; a server might format data based on the user's locale, or it could be that a client machine does the formatting. The same goes for parsing data, and locale-sensitive analysis of data.