CLDR-19123 site: update CLDR 42-43-44 wording around keyboard files

docs/site/downloads/cldr-43.md

@@ -247,6 +247,9 @@ The CLDR language matching data can *and should* be overridden whenever there is
 	- Likely Subtags now have an attribute to indicate the **origin** of the data. This is informational, and typically be ignored by implementations.
 - **Turkey / Türkiye**
 	- In v42, the customary English name for the country code TR was "Turkey", and an alternate name was "Türkiye". In v43, the customary English name was changed to "Türkiye", and the alternate name was set to "Turkey". Translators were advised of the change, and reviewed the names in their locales to see if any needed adjustment. Implementations that wish to retain the English name "Turkey" may choose to use the alternate form.
+- **Keyboards**
+	- The [CLDR Keyboard Working Group] is working on a major overhaul of the Keyboard specification, [released in version 44][44-keyboards]. “Keyboard 3.0” has a very different goal and therefore existing keyboard files do not interoperate, have not been maintained, and will be removed.
+
 
 ## Known Issues
 
@@ -261,3 +264,5 @@ The Unicode [Terms of Use](https://unicode.org/copyright.html) apply to CLDR dat
 
 For web pages with different views of CLDR data, see <https://cldr.unicode.org/index/charts>.
 
+[Keyboard WG]: /index/keyboard-workgroup.md
+[44-keyboards]: /downloads/cldr-44.md#keyboard-changes

docs/site/downloads/cldr-44.md

@@ -156,13 +156,15 @@ The following is a summary of the DTD changes which reflect changes in the struc
 
 ### Keyboard Changes
 
-**Keyboard** has a new DTD (keyboard3\.dtd and the \<keyboard3\> element). This is a complete rewrite of the specification by the Keyboard Subcommittee, and is available as a technical preview in CLDR version 44\. See [TR35 Part 7: Keyboards](https://www.unicode.org/reports/tr35/tr35-keyboards.html). The prior DTDs are included in CLDR but are not used by CLDR data or tooling. **Note**: prior keyboard data files are not compatible, were not maintained and have also been removed.
+**Keyboard** has a new DTD (keyboard3\.dtd and the \<keyboard3\> element). This is a complete rewrite of the specification by the CLDR Keyboard Working Group, and is available as a technical preview in CLDR version 44\. See [TR35 Part 7: Keyboards](https://www.unicode.org/reports/tr35/tr35-keyboards.html). The prior DTDs are included in CLDR but are not used by CLDR data or tooling.
 
 Note that there are additional sample keyboard data files in progress which were not complete for v44, but may be consulted as samples:
 
 - Bengali, Assamese Phonetic Keyboard (PR \#[3368](https://github.com/unicode-org/cldr/pull/3368))
 - French AZERTY optimisé (PR \#[3220](https://github.com/unicode-org/cldr/pull/3220))
 
+**Note**: Prior keyboard data files are not compatible, have not been maintained and have also been removed in CLDR v44. The prior keyboard files are still available from earlier CLDR downloads, but are not recommended for use as they are known to be incorrect and are not compatible with the current DTD.
+
 See the *Known Issues* section for additional known issues.
 
 ## Specification Changes

docs/site/index/keyboard-workgroup.md

@@ -4,7 +4,7 @@ title: CLDR Keyboard Working Group
 
 # CLDR Keyboard Working Group
 
-The CLDR Keyboard Subcommittee is responsible for the development and maintenance of a standard cross-platform XML format for use by keyboard authors.
+The CLDR Keyboard Working Group is responsible for the development and maintenance of a standard cross-platform XML format for use by keyboard authors.
 
 ## Background
 
@@ -24,7 +24,7 @@ There is no central repository or contact point for this data, meaning that such
 
 ## LDML: The universal interchange format for keyboards
 
-The CLDR Keyboard Subcommittee is currently rewriting and redeveloping the existing LDML (XML) definition for keyboards (UTS#35 part 7) in order to define core keyboard-based text input requirements for the world's languages. This format allows the physical and virtual (on-screen or touch) keyboard layouts for a language to be defined in a single file. Input Method Editors (IME) or other input methods are not currently in scope for this format.
+The CLDR Keyboard Working Group is currently rewriting and redeveloping the existing LDML (XML) definition for keyboards (UTS#35 part 7) in order to define core keyboard-based text input requirements for the world's languages. This format allows the physical and virtual (on-screen or touch) keyboard layouts for a language to be defined in a single file. Input Method Editors (IME) or other input methods are not currently in scope for this format.
 
 ![alt-text](../images/keyboard-workgroup-rowkeys.png)
 
@@ -57,7 +57,7 @@ The LDML keyboard format, and the CLDR repository, will make it much easier to d
 
 In 2012, the original LDML keyboard format was designed to describe keyboards for comparative purposes. In 2018, a [PRI was created](http://blog.unicode.org/2018/01/unicode-ldml-keyboard-enhancements.html) soliciting further feedback.
 
-The CLDR Keyboard Subcommittee was formed and has been meeting since mid-2020. It quickly became apparent that the existing LDML format was insufficient for implementing new keyboard layouts.
+The CLDR Keyboard Working Group was formed and has been meeting since mid-2020. It quickly became apparent that the existing LDML format was insufficient for implementing new keyboard layouts.
 
 ### What is the current status?
 
@@ -75,5 +75,5 @@ Implementations
 
 ### How can I get involved?
 
-If you want to be engaged in this workgroup, please contact the CLDR Keyboard Subcommittee via the [Unicode contact form](https://corp.unicode.org/reporting/staff-contact.html).
+If you want to be engaged in this workgroup, please contact the CLDR Keyboard Working Group via the [Unicode contact form](https://unicode.org/reporting.html).