diff --git a/specification/resources/floating_ips/responses/floating_ip_created.yml b/specification/resources/floating_ips/responses/floating_ip_created.yml
index 105bc9f2e..336c49255 100644
--- a/specification/resources/floating_ips/responses/floating_ip_created.yml
+++ b/specification/resources/floating_ips/responses/floating_ip_created.yml
@@ -1,4 +1,5 @@
-description: The response will be a JSON object with a key called `floating_ip`.
+description: |
+  The response will be a JSON object with a key called `floating_ip`.
   The value of this will be an object that contains the standard attributes
   associated with a floating IP.
 
@@ -37,4 +38,4 @@ content:
       floating_ip_assigning:
         $ref: 'examples.yml#/floating_ip_assigning'
       floating_ip_reserving:
-        $ref: 'examples.yml#/floating_ip_reserving'
\ No newline at end of file
+        $ref: 'examples.yml#/floating_ip_reserving'
diff --git a/specification/resources/load_balancers/models/load_balancer_base.yml b/specification/resources/load_balancers/models/load_balancer_base.yml
index 747e9a57a..c606d0ca7 100644
--- a/specification/resources/load_balancers/models/load_balancer_base.yml
+++ b/specification/resources/load_balancers/models/load_balancer_base.yml
@@ -59,7 +59,8 @@ properties:
     deprecated: true
     default: lb-small
     example: lb-small
-    description: This field has been replaced by the `size_unit` field for all
+    description: |
+      This field has been replaced by the `size_unit` field for all
       regions except in AMS2, NYC2, and SFO1. Each available load balancer size
       now equates to the load balancer having a set number of nodes.
 
diff --git a/specification/resources/reserved_ips/responses/reserved_ip_created.yml b/specification/resources/reserved_ips/responses/reserved_ip_created.yml
index 1d800c88a..0ecdb382f 100644
--- a/specification/resources/reserved_ips/responses/reserved_ip_created.yml
+++ b/specification/resources/reserved_ips/responses/reserved_ip_created.yml
@@ -1,4 +1,5 @@
-description: The response will be a JSON object with a key called `reserved_ip`.
+description: |
+  The response will be a JSON object with a key called `reserved_ip`.
   The value of this will be an object that contains the standard attributes
   associated with a reserved IP.