diff --git a/CONTRIBUTORS.md b/CONTRIBUTORS.md
index 8f6a7f2091c1f2..59c01e123c5465 100644
--- a/CONTRIBUTORS.md
+++ b/CONTRIBUTORS.md
@@ -80,3 +80,4 @@ This list is manually curated to include valuable contributions by volunteers th
 | @dixitadusara | |
 | @ameeker | |
 | @StaggerLeee | |
+| @jblz | |
diff --git a/element/README.md b/element/README.md
index de69ef720523ae..514cbffa1ba655 100644
--- a/element/README.md
+++ b/element/README.md
@@ -5,7 +5,7 @@ Element is, quite simply, an abstraction layer atop [React](https://facebook.git
 
 You may find yourself asking, "Why an abstraction layer?". For a few reasons:
 
-- In many applications, especially those extended by a rich plugin ecosystem as is the case with WordPress, it's wise to create interfaces to underlying third-party code. The thinking is that if ever a need arises to change or even replace the underlying implementation, it can be done without catestrophic rippling effects to dependent code, so long as the interface stays the same.
+- In many applications, especially those extended by a rich plugin ecosystem as is the case with WordPress, it's wise to create interfaces to underlying third-party code. The thinking is that if ever a need arises to change or even replace the underlying implementation, it can be done without catastrophic rippling effects to dependent code, so long as the interface stays the same.
 - It provides a mechanism to shield implementers by omitting features with uncertain futures (`createClass`, `PropTypes`).
 - It helps avoid incompatibilities between versions by ensuring that every plugin operates on a single centralized version of the code.