refresh markdown files with latest markdownlint
The latest markdownlint seems to have had minor formatting changes,
which are now being observed in Jenkins. Refresh the files.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I3799a80392b322fe1f0d0eae4fc8a3509a4ebeb9
diff --git a/yaml/com/ibm/ipzvpd/README.md b/yaml/com/ibm/ipzvpd/README.md
index 839a114..9a0d005 100644
--- a/yaml/com/ibm/ipzvpd/README.md
+++ b/yaml/com/ibm/ipzvpd/README.md
@@ -5,12 +5,12 @@
value). Keywords are grouped into records, usually with similar function grouped
into a single record.
-The [OpenPower VPD] [1] format is quite similar to the IPZ format and describes
+The [OpenPower VPD][1] format is quite similar to the IPZ format and describes
the record-keyword structure.
-Also refer to the [VPD Collection design document] [2] that describes how the
-VPD collection application on the BMC will parse and publish the VPD data for
-IBM Power systems on D-Bus.
+Also refer to the [VPD Collection design document][2] that describes how the VPD
+collection application on the BMC will parse and publish the VPD data for IBM
+Power systems on D-Bus.
The D-Bus interfaces defined here describe how IPZ VPD will be made available on
D-Bus. Each YAML here represents a record in the IPZ VPD and keywords that
diff --git a/yaml/xyz/openbmc_project/Software/README.md b/yaml/xyz/openbmc_project/Software/README.md
index 9f11d65..66ed4a3 100644
--- a/yaml/xyz/openbmc_project/Software/README.md
+++ b/yaml/xyz/openbmc_project/Software/README.md
@@ -27,11 +27,11 @@
`xyz.openbmc_project.Common.FilePath` interface would be provided to specify the
location of the image.
-It is assumed that the _ImageManager_ has [at least] a bare minimum amount of
-parsing knowledge, perhaps due to a common image format, to allow it to populate
-all of the properties of `xyz.openbmc_project.Software.Version` and
-`xyz.openbmc_project.Inventory.Decorator.Compatible`. _ItemUpdater_(s) will
-likely listen for standard D-Bus signals to identify new images being created.
+It is assumed that the _ImageManager_ has [at least] a bare minimum amount of parsing
+knowledge, perhaps due to a common image format, to allow it to populate all of the
+properties of `xyz.openbmc_project.Software.Version` and `xyz.openbmc_project.Inventory.Decorator.Compatible`.
+_ItemUpdater_(s) will likely listen for standard D-Bus signals to identify new images
+being created.
### ItemUpdater