docs: 1841 Fix typo and align template divs (#1842)

The div in the section.html layout template uses the wrong column
CSS class for alignment. The divs in the content area for some pages
don't align vertically.

This change uses a different CSS class for aligning columns.

Closes #1841
Signed-off-by: Mike Barkas <[email protected]>

CONTRIBUTORS.md

@@ -55,4 +55,5 @@ and we will add you. **All** contributors belong here. 💯
 * [Ritesh Yadav](https://github.com/DARK-art108)
 * [Jérémy Audiger](https://github.com/jaudiger)
 * [Om More](https://github.com/thisisommore)
-* [Avinash Upadhyaya](https://github.com/avinashupadhya99)
+* [Avinash Upadhyaya](https://github.com/avinashupadhya99)
+* [Mike Barkas](https://github.com/mikebarkas)

docs/content/mixin-dev-guide/architecture.md

@@ -9,7 +9,7 @@ Porter provides two major capabilities: a bundle building capability and with a
 
 A cloud native application bundle built with Porter consists of two main components: the Porter runtime and a declarative manifest file named `porter.yaml`.
 
-The Porter runtime provides the entry point for the bundle and is responsible for executing the desired functionality that has been expressed in the `porter.yaml`. The `porter.yaml` declares what should happen for bundle action. Each bundle action is defined as one or more operations, or steps. Each step definition defines a discrete piece of functionality, such installing a Helm chart or creating a service in a cloud provider. The Porter runtime is responsible for executing each step, but does not implement the desired functionality itself. The functionality declared in each step is actually provided by components called mixins. Porter invokes the mixin by passing the relevant section of the `porter.yaml` to the mixin via standard input. The mixin accepts the YAML document that describes the desired result and performs the desired action. Once finished, the mixin wil write any desired outputs to standard out and return control to the Porter runtime.
+The Porter runtime provides the entry point for the bundle and is responsible for executing the desired functionality that has been expressed in the `porter.yaml`. The `porter.yaml` declares what should happen for bundle action. Each bundle action is defined as one or more operations, or steps. Each step definition defines a discrete piece of functionality, such installing a Helm chart or creating a service in a cloud provider. The Porter runtime is responsible for executing each step, but does not implement the desired functionality itself. The functionality declared in each step is actually provided by components called mixins. Porter invokes the mixin by passing the relevant section of the `porter.yaml` to the mixin via standard input. The mixin accepts the YAML document that describes the desired result and performs the desired action. Once finished, the mixin will write any desired outputs to standard out and return control to the Porter runtime.
 
 For example, a bundle author may wish to execute a bash command. The author would include the `exec` mixin in the mixins section of the porter.yaml and then create a step that defines the desired bash command. For example, the following bundle example would execute `bash -c "echo Hello World"`:
 

docs/themes/porter/layouts/_default/section.html

@@ -7,7 +7,7 @@
       {{ partial "topbar.html" . }}
 
       <div class="row full-width">
-        <div class="small-12 small-1 columns">&nbsp;</div>
+        <div class="small-12 medium-1 columns">&nbsp;</div>
         <div class="small-12 medium-10 columns list-wrap">
           <h1>{{ .Title }}</h1>
           {{ .Content }}