Updating our messaging to reflect our updated repository shortname

Author: JaninaSajka

messaging/to-comment.md

@@ -1,6 +1,6 @@
 For in-progress updates to the document, see the Editors' Draft at:
 
-https://w3c.github.io/adapt-registry/
+https://w3c.github.io/aac-registry/
 
 To comment, please use one of the following two methods:
 

messaging/tweet.md

@@ -1 +1 @@
-W3C announces the First Public Working Draft of *WAI-Adapt Registry for AAC Symbols*: https://www.w3.org/TR/adapt-registry/, providing first-time support for interoperable Augmentative and Alternative Communication (AAC) symbols support in web content.
+W3C announces the First Public Working Draft of *WAI-Adapt Registry for AAC Symbols*: https://www.w3.org/TR/aac-registry/, providing first-time support for interoperable Augmentative and Alternative Communication (AAC) symbols support in web content.

messaging/w3c-news.md

@@ -1,7 +1,7 @@
 WAI News:
 FOR REVIEW: *WAI-Adapt Registry for AAC Symbols* First Public Draft Registry specification
 
-The Accessible Platform Architectures (APA) WAI-Adapt Task Force (WAI-Adapt) welcomes feedback on the first public Draft Registry specification of the [WAI-Adapt Registry for AAC Symbols](https://www.w3.org/TR/adapt-registry/).
+The Accessible Platform Architectures (APA) WAI-Adapt Task Force (WAI-Adapt) welcomes feedback on the first public Draft Registry specification of the [WAI-Adapt Registry for AAC Symbols](https://www.w3.org/TR/aac-registry/).
 
 The purpose of this specification is to support Augmentative and Alternative Communication (AAC) symbols in web content. Millions of users comprehend AAC symbols better than standard text, but there are multiple AAC symbol sets and they are not mutually comprehensible. To solve this issue and make it possible for content creators to support AAC users in web content, this specification:
 
@@ -20,7 +20,7 @@ The purpose of this specification is to support Augmentative and Alternative Com
 
 For in-progress updates to the document, see the Editors' Draft at:
 
-https://w3c.github.io/adapt-registry/
+https://w3c.github.io/aac-registry/
 
 To comment, please use one of the following two methods:
 

messaging/wai-announce-email.txt

@@ -4,15 +4,15 @@ W3C WAI invites you to comment on the First Public Working Draft of:
 
 WAI-Adapt Registry for AAC Symbols
 
-https://www.w3.org/TR/adapt-registry/
+https://www.w3.org/TR/aac-registry/
 
 *** Overview***
 
 \*The WAI-Adapt Registry provides an extensible registry for the Blissymbolics Communication International (BCI) concept index. This index provides a mapping between concepts expressed in standard text and  corresponding symbols in major Augmentative and Alternative Communication (AAC) symbol sets in use today.
 
 For in-progress updates to the document, see the Editors' Draft at:
 
-https://w3c.github.io/adapt-registry/
+https://w3c.github.io/aac-registry/
 
 To comment, please use one of the following two methods:
 
@@ -34,7 +34,8 @@ Please send comments by Friday 13 January 2023.
 We encourage you to share this information widely. Please include @w3c_wai, @w3c,
 #accessibility, #a11y, @@ Here's a tweet text you can use:
 
-W3C announces the First Public Working Draft of *WAI-Adapt Registry for AAC Symbols*: https://www.w3.org/TR/adapt-registry/, providing first-time support for interoperable Augmentative and Alternative Communication (AAC) symbols support in web content.
+W3C announces the First Public Working Draft of *WAI-Adapt Registry for AAC
+Symbols*: https://www.w3.org/TR/aac-registry/, providing first-time support for interoperable Augmentative and Alternative Communication (AAC) symbols support in web content.
 
 Regards,