reformat with latest settings
Reformat with the latest settings from openbmc-build-scripts (and
copy latest config files where appropriate). Fix a few minor
markdownlint issues.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I55205817c29dc3f182a165ddf9cd5d4e07b90063
diff --git a/yaml/xyz/openbmc_project/Software/RequestedRedundancyPriority.interface.yaml b/yaml/xyz/openbmc_project/Software/RequestedRedundancyPriority.interface.yaml
index 141b147..2491a86 100644
--- a/yaml/xyz/openbmc_project/Software/RequestedRedundancyPriority.interface.yaml
+++ b/yaml/xyz/openbmc_project/Software/RequestedRedundancyPriority.interface.yaml
@@ -6,9 +6,9 @@
type: byte
default: 0
description: >
- Upon Activation of the software Version, the *ItemUpdater*
- should attempt to activate the software version such that
- the resulting `Software.RedundancyPriority.Priority` is Priority.
+ Upon Activation of the software Version, the *ItemUpdater* should
+ attempt to activate the software version such that the resulting
+ `Software.RedundancyPriority.Priority` is Priority.
See `Software.RedundancyPriority.Priority` for valid values and
definitions.
@@ -16,5 +16,5 @@
By default, any Activation should be done to the highest priority.
Some *ItemUpdater* implementations may be unable to apply this
`RequestedRedundancyPriority.Priority`, resulting in an
- `ActivationState` which is either `Failed` or `Active` with
- `Priority` of `0 (High)`.
+ `ActivationState` which is either `Failed` or `Active` with `Priority`
+ of `0 (High)`.