guide: fix markdown ref links

6 files changed, 9 insertions, 9 deletions

diff --git a/guide/src/entity_container.md b/guide/src/entity_container.md
index f6568044..e20e9096 100644
--- a/guide/src/entity_container.md
+++ b/guide/src/entity_container.md
@@ -25,9 +25,9 @@
 #### `extra` Fields
 
 - `abbrev` (string): a commonly used abbreviation for the publication, as used
-  in citations, following the [ISO 4]() standard. Eg, "Journal of Polymer
+  in citations, following the [ISO 4][] standard. Eg, "Journal of Polymer
   Science Part A" -> "J. Polym. Sci. A"
-- `coden` (string): an external identifier, the [CODEN code](). 6 characters,
+- `coden` (string): an external identifier, the [CODEN code][]. 6 characters,
   all upper-case.
 - `issnp` (string): Print ISSN
 - `issne` (string): Electronic ISSN
diff --git a/guide/src/entity_release.md b/guide/src/entity_release.md
index 872708a2..27ce0f2c 100644
--- a/guide/src/entity_release.md
+++ b/guide/src/entity_release.md
@@ -144,7 +144,7 @@ complete or correct in more obscure cases.
   should *always* be stored will be needed.
 - `core` (string): external identifier for the [CORE] open access
   aggregator. These identifiers are integers, but stored in string format.
-- `arxiv` (string) external identifier to a (version-specific) [arxiv.org]()
+- `arxiv` (string) external identifier to a (version-specific) [arxiv.org][]
   work. For releases, must always include the `vN` suffix (eg, `v3`).
 - `jstor` (string) external identifier for works in JSTOR.
 - `ark` (string) ARK identifer
diff --git a/guide/src/goals.md b/guide/src/goals.md
index 9bb64b62..c0654df2 100644
--- a/guide/src/goals.md
+++ b/guide/src/goals.md
@@ -11,8 +11,8 @@ The Internet Archive has two primary use cases for Fatcat:
 In the larger ecosystem, Fatcat could also provide:
 
 - A work-level (as opposed to title-level) archival dashboard: what fraction of
-  all published works are preserved in archives? [KBART](), [CLOCKSS](),
-  [Portico](), and other preservation networks don't provide granular metadata
+  all published works are preserved in archives? [KBART][], [CLOCKSS][],
+  [Portico][], and other preservation networks don't provide granular metadata
 - A collaborative, independent, non-commercial, fully-open, field-agnostic,
   "completeness"-oriented catalog of scholarly metadata
 - Unified (centralized) foundation for discovery and access across repositories
diff --git a/guide/src/sources.md b/guide/src/sources.md
index 5b3d9d3e..b9372848 100644
--- a/guide/src/sources.md
+++ b/guide/src/sources.md
@@ -3,7 +3,7 @@
 The core metadata bootstrap sources, by entity type, are:
 
 - `releases`: Crossref metadata, with DOIs as the primary identifier, and
-  PubMed (central), Wikidata, and [CORE]() identifiers cross-referenced
+  PubMed (central), Wikidata, and [CORE][] identifiers cross-referenced
 - `containers`: munged metadata from the DOAJ, ROAD, and Norwegian journal
   list, with ISSN-Ls as the primary identifier. ISSN provides an "ISSN to
   ISSN-L" mapping to normalize electronic and print ISSN numbers.
diff --git a/guide/src/style_guide.md b/guide/src/style_guide.md
index d670691a..87d5e74a 100644
--- a/guide/src/style_guide.md
+++ b/guide/src/style_guide.md
@@ -20,7 +20,7 @@ documentation (such as DOI `10.5555/12345678`) are allowed (and the entity
 should be tagged as a fake or example). Non-registered "identifier-like
 strings", which are semantically valid but not registered, should not exist in
 Fatcat metadata in an identifier column. Invalid identifier strings can be
-stored in "extra" metadata. Crossref has [blogged]() about this distinction.
+stored in "extra" metadata. Crossref has [blogged][] about this distinction.
 
 [blogged]: https://www.crossref.org/blog/doi-like-strings-and-fake-dois/
 
@@ -33,7 +33,7 @@ bots.
 DOIs should *always* be stored and transferred in lower-case form. Note that
 there are almost no other constraints on DOIs (and handles in general): they
 may have multiple forward slashes, whitespace, of arbitrary length, etc.
-Crossref has a [number of examples]() of such "valid" but frustratingly
+Crossref has a [number of examples][] of such "valid" but frustratingly
 formatted strings.
 
 [number of examples]: https://www.crossref.org/blog/dois-unambiguously-and-persistently-identify-published-trustworthy-citable-online-scholarly-literature-right/
diff --git a/guide/src/welcome.md b/guide/src/welcome.md
index 4c234c0a..c3c736da 100644
--- a/guide/src/welcome.md
+++ b/guide/src/welcome.md
@@ -26,7 +26,7 @@ See [Policies](./policies.md) for licensing details, and
 [Sources](./sources.md) for attribution of the foundational metadata corpuses
 we build on top of.
 
-Fatcat is currently used internally at the [Internet Archive](), but interested
+Fatcat is currently used internally at the [Internet Archive][], but interested
 folks are welcome to contribute to it's design and development, and we hope to
 ultimately crowd-source corrections and additional to bibliographic metadata,
 and receive direct automated feeds of new content.