diff --git a/library/cloud/vpc b/library/cloud/vpc
index e93dbcfe7a..8ecab435c1 100644
--- a/library/cloud/vpc
+++ b/library/cloud/vpc
@@ -24,7 +24,7 @@ version_added: "1.4"
 options:
   cidr_block:
     description:
-      - The cidr block representing the VPC, e.g. 10.0.0.0/16
+      - "The cidr block representing the VPC, e.g. 10.0.0.0/16"
     required: false, unless state=present
   dns_support:
     description:
@@ -40,7 +40,7 @@ options:
     choices: [ "yes", "no" ]
   subnets:
     description:
-      - A dictionary array of subnets to add of the form: { cidr: ..., az: ... }. Where az is the desired availability zone of the subnet, but it is not required. All VPC subnets not in this list will be removed.
+      - "A dictionary array of subnets to add of the form: { cidr: ..., az: ... }. Where az is the desired availability zone of the subnet, but it is not required. All VPC subnets not in this list will be removed."
     required: false
     default: null
     aliases: []
@@ -59,7 +59,7 @@ options:
     aliases: []
   route_tables:
     description:
-      - A dictionary array of route tables to add of the form: { subnets: [172.22.2.0/24, 172.22.3.0/24,], routes: [{ dest: 0.0.0.0/0, gw: igw},] }. Where the subnets list is those subnets the route table should be associated with, and the routes list is a list of routes to be in the table.  The special keyword for the gw of igw specifies that you should the route should go through the internet gateway attached to the VPC. gw also accepts instance-ids in addition igw. This module is currently unable to affect the 'main' route table due to some limitations in boto, so you must explicitly define the associated subnets or they will be attached to the main table implicitly.
+      - "A dictionary array of route tables to add of the form: { subnets: [172.22.2.0/24, 172.22.3.0/24,], routes: [{ dest: 0.0.0.0/0, gw: igw},] }. Where the subnets list is those subnets the route table should be associated with, and the routes list is a list of routes to be in the table.  The special keyword for the gw of igw specifies that you should the route should go through the internet gateway attached to the VPC. gw also accepts instance-ids in addition igw. This module is currently unable to affect the 'main' route table due to some limitations in boto, so you must explicitly define the associated subnets or they will be attached to the main table implicitly."
     required: false
     default: null
     aliases: []