Address feedback

Author: Zack Chase

content/docs/intro/vs/cloud_templates.md

@@ -1,5 +1,5 @@
 ---
-title: Pulumi vs. AWS CloudFormation and Other Templates | Pulumi
+title: Pulumi vs. AWS CloudFormation and Other Templates
 meta_desc: This page gives an overview of the major differences between Pulumi and Cloud Templates such as AWS CloudFormation.
 linktitle: Cloud Templates
 menu:
@@ -10,29 +10,25 @@ menu:
 aliases: ["/docs/reference/vs/cloud_templates/"]
 ---
 
-What is Pulumi?
-
-Pulumi offers a multi-cloud alternative to typical, more restrictive infrastructure-as-code template solutions, such as AWS CloudFormation. Pulumi allows you to streamline processes through managing resources from different platforms all in one place, using real code, in your favorite language.
-
-What is CloudFormation?
+## What is CloudFormation?
 
 All major cloud providers offer their own form of infrastructure-as-"code" solution, typically by way of JSON or
 YAML-based templating solutions. This includes AWS CloudFormation and Azure Resource Manager (ARM) templates.
 
 These markup-based configuration files are often uploaded to a hosted service in the target cloud, where a hosted
 service will then process the files to create, update, or delete resources as necessary.
 
-The Pulumi Difference
+## The Pulumi Difference
 
-Pulumi's model shares a lot with these systems. Although Pulumi programs are written in imperative, familiar languages,
-they are ultimately evaluated to produce a similar set of create, update, or delete operations for your cloud resources.
+Pulumi offers a multi-cloud alternative to more restrictive infrastructure-as-code template solutions, such as AWS CloudFormation. Pulumi allows you to streamline processes through managing resources from different platforms all in one place, using real code, in your favorite language.
 
-This is where Pulumi begins to diverge from these other solutions such as AWS CloudFormation, however.
+Pulumi's model shares a lot with these systems. Although Pulumi programs are written in imperative, familiar languages,
+they are ultimately evaluated to produce a similar set of create, update, or delete operations for your cloud resources. This is where Pulumi begins to diverge from these other solutions such as AWS CloudFormation, however.
 
-Pulumi lets you use your favorite languages — complete control rather than bespoke templating solutions such as CloudFormation. These templates typically use syntaxes that
-are awkward, hard to learn, and even harder to remember. Pulumi programs are just real code. Thanks to basic things
-like functions and classes, we've seen 25,000 line CloudFormation templates shrink to just a few hundred lines of code.
-This approach also leads to far less copy and pasting between projects because you can share packages.
+Pulumi lets you use your favorite languages, instead of bespoke templating solutions such as CloudFormation. These
+typically use syntaxes that are awkward, hard to learn, and even harder to remember. Pulumi programs are just real
+code. Thanks to basic things like functions and classes, we've seen 25,000 line CloudFormation templates shrink to
+just a few hundred lines of code. This approach also leads to far less copy and pasting between projects because you can share packages.
 
 Pulumi is also multi-cloud. So, you only need to learn one programming model, tool, and workflow. In fact, you can
 easily manage resources from different clouds, easing what would otherwise require manual orchestration. For example
@@ -49,5 +45,4 @@ There are many community-led projects which allow you to write code in a real la
 configuration templates as a sort of "compilation" step. These offer nice syntactic sugar on top of the raw
 templates, but the underlying model leaks through and carries forward all of the other abovementioned shortcomings.
 
-Finally, Pulumi is [open source](https://github.com/pulumi/pulumi) and community-driven. All of the other cloud systems — such as Azure Automation or AWS CloudFormation — are
-proprietary closed source, lead to lock-in, and lack the ability for the community to contribute to them.
+Finally, Pulumi is [open source](https://github.com/pulumi/pulumi) and community-driven. All of the other cloud systems — such as Azure Resource Manager or AWS CloudFormation — are proprietary closed source, lead to lock-in, and lack the ability for the community to contribute to them.