Yet another rebranding pass

.github/CODEOWNERS

@@ -1,2 +1,2 @@
 # The AEP working group owns the content of this repository.
-*   @aip-dev/aip
+*   @aep-dev/aip

ADOPTERS.md

@@ -8,5 +8,5 @@ name to this list (in alphabetical order).
 
 | Organization                       | Contact                                          | How you use the AEPs                                                                                                                                                                                                                           |
 | ---------------------------------- | ------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| [Google](https://about.google/)    | [@toumorokoshi](https://github.com/toumorokoshi) | Google maintains a fork at [google.aip.dev](http://google.aip.dev) which is adhered to for all APIs. Google also runs the [api-linter](https://linter.aip.dev/) across the company internally.                                                 |
-| [Roblox](https://corp.roblox.com/) | [@rofrankel](https://github.com/rofrankel)       | Roblox maintains a private fork of the AEPs, and is using them as a style guide for new APIs. Roblox also maintains private forks of the [api-linter](https://linter.aip.dev) and [site generator](https://github.com/aip-dev/site-generator). |
+| [Google](https://about.google/)    | [@toumorokoshi](https://github.com/toumorokoshi) | Google maintains a fork at [google.aep.dev](http://google.aep.dev) which is adhered to for all APIs. Google also runs the [api-linter](https://linter.aep.dev/) across the company internally.                                                 |
+| [Roblox](https://corp.roblox.com/) | [@rofrankel](https://github.com/rofrankel)       | Roblox maintains a private fork of the AEPs, and is using them as a style guide for new APIs. Roblox also maintains private forks of the [api-linter](https://linter.aep.dev) and [site generator](https://github.com/aep-dev/site-generator). |

CONTRIBUTING.md

@@ -45,7 +45,7 @@ how to do so correctly is:
   [pyenv][5] is probably the best way if you have other Python projects).
 - Create a Python 3.8 [venv][6]. Once it is created, activate it in your shell
   (`source path/to/venv/bin/activate`).
-- `pip install git+https://github.com/aip-dev/site-generator.git`
+- `pip install git+https://github.com/aep-dev/site-generator.git`
 - `aep-site-serve .`
 
 ## Contributor License Agreement
@@ -74,7 +74,7 @@ to ensure a consistent style throughout our source. You can add prettier as a
 plugin in most development environments.
 
 [1]: https://pages.github.com/
-[2]: https://github.com/aip-dev/site-generator
+[2]: https://github.com/aep-dev/site-generator
 [3]: https://docker.com/
 [4]: https://prettier.io/
 [5]: https://github.com/pyenv/pyenv

OWNERS.md

@@ -19,7 +19,7 @@ approval privileges to the aep-dev organization.
 
 ## Emiritus
 
-The following table enumerates previous maintainers of aip.dev, the original
+The following table enumerates previous maintainers of aep.dev, the original
 style guide from which aep.dev was forked.
 
 | Name            | GitHub                                               | Organization |

aep/general/0001/aep.md

@@ -27,22 +27,22 @@ metadata in the AEP GitHub repository.
 
 Companies **may** adopt the AEP system in one of two ways:
 
-- By applying the guidance described at [aip.dev][].
+- By applying the guidance described at [aep.dev][].
 - By "forking" the AEP system and setting up their own subdomain.
 
 Companies with an already-established corpus of services are unlikely to have
-exactly followed the guidance at [aip.dev][]. Forking the system is valuable
+exactly followed the guidance at [aep.dev][]. Forking the system is valuable
 because the guidance becomes comparable. Forks **must** retain the same
 numbering system (AEP-2) to provide that comparability.
 
 ### Technical leadership
 
-The AEP system, as well as the guidance on [aip.dev][], is overseen by the AEP
+The AEP system, as well as the guidance on [aep.dev][], is overseen by the AEP
 technical steering committee. The committee is the set of people who make
 decisions on AEPs. The general goal is that the AEP process is collaborative
 and that we largely work on the basis of consensus. However, a limited number
 of designated approvers is necessary, and these committee members will be
-approvers for each AEP on [aip.dev][].
+approvers for each AEP on [aep.dev][].
 
 The technical steering committee membership is currently:
 
@@ -60,7 +60,7 @@ sentence structure, markup, etc.).
 Committee membership is by invitation of the current committee. The committee
 **must not** include more than two members from the same company.
 
-**Note:** Companies that maintain their own fork of [aip.dev][] select their
+**Note:** Companies that maintain their own fork of [aep.dev][] select their
 own leadership and have full control of their fork's content.
 
 ## States
@@ -218,4 +218,4 @@ then the technical steering committee **should** create a new AEP that, once
 approved, will replace the old one. The old one then enters "Replaced" state,
 and will link to the new, current AEP.
 
-[aip.dev]: https://aip.dev/
+[aep.dev]: https://aep.dev/