Fixes in style and more on CDK (#5292)

* Fixes in style and more on CDK

* Addressing review comments

docs/getting-started-guides/ubuntu/security.md

@@ -3,22 +3,24 @@ title: Security Considerations
 ---
 
 {% capture overview %}
+By default all connections between every provided node are secured via TLS by easyrsa, including the etcd cluster.
+
 This page explains the security considerations of a deployed cluster and production recommendations.
 {% endcapture %}
 {% capture prerequisites %}
 This page assumes you have a working Juju deployed cluster.
 {% endcapture %}
 
-By default all connections between every provided node is secured via TLS by easyrsa, including the etcd cluster. 
 
+{% capture steps %}
 ## Implementation
 
-The TLS and easyrsa implementations use the following [layers](https://jujucharms.com/docs/2.0/developer-layers). 
+The TLS and easyrsa implementations use the following [layers](https://jujucharms.com/docs/2.2/developer-layers).
 
 [layer-tls-client](https://github.com/juju-solutions/layer-tls-client)
 [layer-easyrsa](https://github.com/juju-solutions/layer-easyrsa)
 
-{% capture steps %}
+
 ## Limiting ssh access
 
 By default the administrator can ssh to any deployed node in a cluster. You can mass disable ssh access to the cluster nodes by issuing the following command.
@@ -27,7 +29,7 @@ By default the administrator can ssh to any deployed node in a cluster. You can
 
 Note: The Juju controller node will still have open ssh access in your cloud, and will be used as a jump host in this case.
 
-Refer to the [model management](https://jujucharms.com/docs/2.0/models) page in the Juju documentation for instructions on how to manage ssh keys.
+Refer to the [model management](https://jujucharms.com/docs/2.2/models) page in the Juju documentation for instructions on how to manage ssh keys.
 {% endcapture %}
 
 {% include templates/task.md %}