Fix naming

docs/code-of-conduct.md

@@ -59,7 +59,7 @@ further defined and clarified by project maintainers.
 ## Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at [contact@isiahmeadows.com](mailto:contact@isiahmeadows.com?subject=Mithril%20Code%20of%20Conduct). All
+reported by contacting the project team at [contact@claudiameadows.dev](mailto:contact@claudiameadows.dev?subject=Mithril%20Code%20of%20Conduct). All
 complaints will be reviewed and investigated and will result in a response that
 is deemed necessary and appropriate to the circumstances. The project team is
 obligated to maintain confidentiality with regard to the reporter of an incident.

docs/credits.md

@@ -9,7 +9,7 @@ Mithril.js was originally written by Leo Horie, but it is where it is today than
 Special thanks to:
 
 - Pat Cavit, who exposed most of the public API for Mithril.js 1.0, brought in test coverage and automated the publishing process
-- Isiah Meadows, who brought in linting, modernized the test suite and has been a strong voice in design discussions
+- Claudia Meadows, who brought in linting, modernized the test suite and has been a strong voice in design discussions
 - Zoli Kahan, who replaced the original Promise implementation with one that actually worked properly
 - Alec Embke, who single-handedly wrote the JSON-P implementation
 - Barney Carroll, who suggested many great ideas and relentlessly pushed Mithril.js to the limit to uncover design issues prior to Mithril.js 1.0

docs/jsx.md

@@ -267,7 +267,7 @@ JSX and hyperscript are two different syntaxes you can use for specifying vnodes
 
 -   Hyperscript is more approachable if you come from a backend JS background that doesn't involve much HTML or XML. It's more concise with less redundancy, and it provides a CSS-like sugar for static classes, IDs, and other attributes. It also can be used with no build step at all, although [you can add one if you wish](https://github.com/MithrilJS/mopt). And it's slightly easier to work with in the face of a lot of dynamic content, because you don't need to "interpolate" anything. However, the terseness does make it harder to read for some people, especially those less experienced and coming from a front end HTML/CSS/XML background, and I'm not aware of any plugins that auto-complete parts of hyperscript selectors like IDs, classes, and attributes.
 
-You can see the tradeoffs come into play in more complex trees. For instance, consider this hyperscript tree, adapted from a real-world project by [@isiahmeadows](https://github.com/isiahmeadows/) with some alterations for clarity and readability:
+You can see the tradeoffs come into play in more complex trees. For instance, consider this hyperscript tree, adapted from a real-world project by [@dead-claudia](https://github.com/dead-claudia) with some alterations for clarity and readability:
 
 ```javascript
 function SummaryView() {

docs/migration-v02x.md

@@ -879,7 +879,7 @@ Since v2.x uses standards-compliant Promises, `m.sync` is redundant. Use `Promis
 ```javascript
 m.sync([
 	m.request({ method: 'GET', url: 'https://api.github.com/users/lhorie' }),
-	m.request({ method: 'GET', url: 'https://api.github.com/users/isiahmeadows' }),
+	m.request({ method: 'GET', url: 'https://api.github.com/users/dead-claudia' }),
 ])
 .then(function (users) {
 	console.log("Contributors:", users[0].name, "and", users[1].name)
@@ -891,7 +891,7 @@ m.sync([
 ```javascript
 Promise.all([
 	m.request({ method: 'GET', url: 'https://api.github.com/users/lhorie' }),
-	m.request({ method: 'GET', url: 'https://api.github.com/users/isiahmeadows' }),
+	m.request({ method: 'GET', url: 'https://api.github.com/users/dead-claudia' }),
 ])
 .then(function (users) {
 	console.log("Contributors:", users[0].name, "and", users[1].name)