diff --git a/README.md b/README.md
index 565edb1..9c9b9dc 100644
--- a/README.md
+++ b/README.md
@@ -40,7 +40,8 @@
   - The main event log interface.
 - [xyz.openbmc_project.Association.Definitions]
   - Used for specifying inventory items as the cause of the event.
-  - For more information on associations, see [here][associations-doc].
+  - For more information on associations, see the [associations
+    doc][associations-doc].
 - [xyz.openbmc_project.Object.Delete]
   - Provides a Delete method to delete the event.
 - [xyz.openbmc_project.Software.Version]
@@ -54,8 +55,8 @@
 
 The logging daemon has the ability to add `callout` associations to an event log
 based on text in the AdditionalData property. A callout is a link to the
-inventory item(s) that were the cause of the event log. See [here][callout-doc]
-for details.
+inventory item(s) that were the cause of the event log. See [callout
+doc][callout-doc] for details.
 
 ### Creating Event Logs In Code
 
@@ -223,8 +224,8 @@
       an elog-errors.hpp file that just contains the local errors, and check
       that into the repository and include it where the errors are needed.
    2. Create a recipe that copies the local YAML files to a place that
-      phosphor-logging can find it during the build. See [here][led-link] for an
-      example.
+      phosphor-logging can find it during the build. See sample [LED
+      YAML][led-link] for an example.
 
 #### D-Bus Event Log Creation [deprecated]
 
@@ -408,8 +409,8 @@
 
 - OpenPower PELs
   - Enabled with --enable-openpower-pel-extension
-  - Detailed information can be found
-    [here](extensions/openpower-pels/README.md)
+  - Detailed information can be found in
+    [extensions/openpower-pels](extensions/openpower-pels/README.md).
 
 ## Remote Logging via Rsyslog
 
@@ -485,8 +486,8 @@
 severities of Informational or Debug will not block boots, even if they have
 callouts.
 
-The full design for this can be found
-[here](https://github.com/openbmc/docs/blob/master/designs/fail-boot-on-hw-error.md)
+The full design for this can be found in
+[docs](https://github.com/openbmc/docs/blob/master/designs/fail-boot-on-hw-error.md).
 
 To enable this function:
 
diff --git a/extensions/openpower-pels/README.md b/extensions/openpower-pels/README.md
index 7e3bacb..02a26a4 100644
--- a/extensions/openpower-pels/README.md
+++ b/extensions/openpower-pels/README.md
@@ -224,7 +224,7 @@
 ## The PEL Message Registry
 
 The PEL message registry is used to create PELs from OpenBMC event logs.
-Documentation can be found [here](registry/README.md).
+[Documentation](registry/README.md) is available.
 
 ## Callouts
 
diff --git a/extensions/openpower-pels/registry/README.md b/extensions/openpower-pels/registry/README.md
index 27c0044..ba80f39 100644
--- a/extensions/openpower-pels/registry/README.md
+++ b/extensions/openpower-pels/registry/README.md
@@ -30,15 +30,16 @@
 Component IDs will be unique on a per-repository basis for errors unique to that
 repository. When the same errors are created by multiple repositories, those
 errors will all share the same component ID. The master list of component IDs is
-[here](O_component_ids.json). That file can used by PEL parsers to display a
-name for the component ID. The 'O' in the name is the creator ID value for BMC
+[available](O_component_ids.json). That file can used by PEL parsers to display
+a name for the component ID. The 'O' in the name is the creator ID value for BMC
 created PELs.
 
 ## Message Registry Fields
 
-The message registry schema is [here](schema/schema.json), and the message
-registry itself is [here](message_registry.json). The schema will be validated
-either during a bitbake build or during CI, or eventually possibly both.
+The [message registry schema](schema/schema.json) and the
+[message registry](message_registry.json) is available. The schema will be
+validated either during a bitbake build or during CI, or eventually possibly
+both.
 
 In the message registry, there are fields for specifying:
 
@@ -145,8 +146,8 @@
 not supplied the code will fill them in based on those fields.
 
 In fact, even if supplied here, the code may still modify them to ensure they
-are correct. The rules used for this are
-[here](../README.md#action-flags-and-event-type-rules).
+are correct. The rules used for this are in the
+[OpenPower PELs README](../README.md#action-flags-and-event-type-rules).
 
 ```json
 "ActionFlags": ["service_action", "report", "call_home"]
@@ -339,8 +340,8 @@
 The `Systems` can accept the system names as an array of strings and the list of
 callouts common to those systems can be listed under the key.
 
-Available maintenance procedures are listed [here][1] and in the source code
-[here][2].
+Available maintenance procedures are listed in the [parser][1] and in the
+[source code][2].
 
 [1]:
   https://github.com/ibm-openbmc/openpower-pel-parsers/blob/master/modules/calloutparsers/ocallouts/ocallouts.py