diff --git a/README.md b/README.md
index 82043d3..13d0555 100644
--- a/README.md
+++ b/README.md
@@ -11,14 +11,14 @@ In general we expect to focus on developing explainers that:
 * or a counterproposal that is more aligned with the Web Vision than existing technologies or proposals
 
 ## Current Explainers
-* [EyeDropper as <input>](https://github.com/mozilla/explainers/blob/main/eyedropper-input.md)
-* [Amount](https://github.com/mozilla/explainers/blob/main/amount.md)
+* [EyeDropper as <input>](eyedropper-input.md)
+* [Amount](amount.md)
 * [Translation API](translation.md)
 * [Standard Measures with U.S. English](standard-measures-en-us.md)
 * ...
 
 ## Feedback on Explainers
-We strongly prefer external feedback only on explainers that are in their own repo (see [Explainer file progress](#explainer-file-progress)).
+We strongly prefer external feedback only on explainers that are in their own repo (see [Explainer repo progress](#explainer-repo-progress)).
 
 If you see something in a Mozilla Explainer that you want to suggest changing or fixing, please file an issue describing the problem and suggested resolution, not a pull request.  
 Exception: minor non-substantive or typographical changes may be submitted as PRs.
diff --git a/amount.md b/amount.md
index 741e112..d1ec2cf 100644
--- a/amount.md
+++ b/amount.md
@@ -50,7 +50,7 @@ Both elements are also widely natively supported by browsers
 ([MDN data support](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/data#browser_compatibility), 
 [MDN time support](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/time#browser_compatibility)), 
 however without any default user-discernible effects, 
-including [in screen readers](https://twitter.com/LeonieWatson/status/1333078194925264898), 
+including [in screen readers]([https://twitter.com/LeonieWatson/status/1333078194925264898](https://web.archive.org/web/20201129160223/https://twitter.com/LeonieWatson/status/1333078194925264898)), 
 despite the “[First rule of ARIA use](https://www.w3.org/TR/aria-in-html/#rule1)” encouraging publishers to use native HTML semantic elements.
 
 ### Prior proposals
@@ -132,7 +132,7 @@ Proposal: a new HTML `<amount>` element (similar to `<data>` and `<time>`), with
 
 ### currency extension
 As an exploration, to extend the `<amount>` element to support currency, we could do so with:
-* `currency` attribute: optional currency code (([ISO 4217](https://en.wikipedia.org/wiki/ISO_4217)) to express a monetary amount. User agents could use an online exchange service to compute rough equivalents and note the source and time dependency (temporal context) of any such conversions.
+* `currency` attribute: optional currency code ([ISO 4217](https://en.wikipedia.org/wiki/ISO_4217)) to express a monetary amount. User agents could use an online exchange service to compute rough equivalents and note the source and time dependency (temporal context) of any such conversions.
   * e.g. `<amount currency=USD value=64000>$64,000</amount>`
 * The presence of both `unit` and `currency` attributes is an error. The user agent must ignore both attributes.
 * Quantity change: If neither a unit (attribute or parsed) nor `currency` attribute are present, the amount is unitless and expresses a quantity.