diff --git a/yaml/xyz/openbmc_project/Software/ActivationBlocksTransition.interface.yaml b/yaml/xyz/openbmc_project/Software/ActivationBlocksTransition.interface.yaml
index 51fbc8e..f452819 100644
--- a/yaml/xyz/openbmc_project/Software/ActivationBlocksTransition.interface.yaml
+++ b/yaml/xyz/openbmc_project/Software/ActivationBlocksTransition.interface.yaml
@@ -4,10 +4,10 @@
     `Software.Version` is in `Activating` state.
 
     The specific state transition(s) to prevent are left to the implementation.
-    A typical use of this would be to prevent (delay) the power-on of a
-    managed host while the BIOS is being updated.  The managed host, via
-    systemd transitions, might start the power-on sequence and then wait for
-    any object with this `ActivationBlocksTransition` interface to no longer be
-    in `Activating` state.  Causal ordering of dbus operations can prove that
-    no update is currently being performed and the power-on sequence may safely
+    A typical use of this would be to prevent (delay) the power-on of a managed
+    host while the BIOS is being updated.  The managed host, via systemd
+    transitions, might start the power-on sequence and then wait for any object
+    with this `ActivationBlocksTransition` interface to no longer be in
+    `Activating` state.  Causal ordering of dbus operations can prove that no
+    update is currently being performed and the power-on sequence may safely
     continue.