linode · Jskobos · Jan 31, 2018 · Jan 16, 2018 · Jan 16, 2018 · Jan 17, 2018
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
@@ -0,0 +1,73 @@
+# Linode Code of Conduct
+
+## Our Pledge
+
+In order to encourage an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of:
+
+* age
+* body size
+* disability
+* ethnicity
+* gender identity and expression
+* level of experience
+* nationality
+* personal appearance
+* race
+* religion
+* sexual identity and orientation
+
+## Our Standards
+
+You can contribute to creating a positive environment in many ways. For example you can:
+
+* use welcoming and inclusive language
+* be respectful of differing viewpoints and experiences
+* accept constructive criticism gracefully
+* focus on what is best for the community
+* show empathy towards other community members
+* be helpful and understanding
+
+You should not:
+
+* use sexualized language or imagery
+* make unwelcome sexual advances
+* troll, and make insulting or derogatory comments
+* make personal or political attacks
+* harass others, in public or private
+* publish others' private information, such as a physical or electronic address, without explicit permission
+* engage in any other conduct which could reasonably be considered bullying or inappropriate in a professional setting
+
+## Our Responsibilities
+
+As project maintainers, we are responsible for clarifying the standards of acceptable behavior and we are expected to take appropriate and fair corrective action in response to any instances of unacceptable behaviour.
+
+We have the right and responsibility to remove, edit, or reject:
+
+* comments
+* commits
+* code
+* issues
+* other contributions that are not aligned to this code of conduct
+
+We also reserve the right to temporarily or permanently ban any contributor for other behaviors we deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This code of conduct applies whenever you are representing the project or community. For example you may be:
+
+* working in a project space online or in the public
+* using an official project email address
+* posting via an official social media account
+* participating in an online or offline event
+
+Project maintainers may further define and clarify representation of a project.
+
+## Enforcement
+
+You should report any instances of abusive, harassing, or otherwise unacceptable behaviour to the project team at docs@linode.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain the anonymity of the reporter of an incident. We may post further details of specific enforcement policies separately.
+
+Project contributors who do not follow or enforce this code of conduct in good faith may face temporary or permanent consequences. These will be determined by members of the project's leadership.
+
+## Attribution
+
+This code of conduct is adapted from the [Contributor Covenant](http://contributor-covenant.org), version 1.4, and the [gov.uk open standards CODE_OF_CONDUCT.md](https://github.com/alphagov/open-standards/blob/master/CODE_OF_CONDUCT.md).
diff --git a/README.md b/README.md
@@ -1,6 +1,6 @@
 ![Linode logo](docs/assets/linode_readme_logo.png)
 
-# Guides and Tutorials [![License: CC BY 4.0](https://img.shields.io/badge/License-CC%20BY%204.0-blue.svg)](https://creativecommons.org/licenses/by/4.0/)
+# Guides and Tutorials [![License: CC BY 4.0](https://img.shields.io/badge/License-CC%20BY%204.0-blue.svg)](https://creativecommons.org/licenses/by/4.0/) [![first-timers-only](http://img.shields.io/badge/first--timers--only-friendly-blue.svg)](http://www.firsttimersonly.com/)
 
 <img align="right" width="100" height="100" src="docs/assets/linode_readme_book.png">
 
@@ -20,7 +20,7 @@
 
 ## How can I write a guide?
 
-We are constantly looking to impove the quality of our library. See our [rotating list of suggested topics](https://www.linode.com/docs/contribute/).
+We are constantly looking to improve the quality of our library. See our [rotating list of suggested topics](https://www.linode.com/docs/contribute/).
 
 More detailed instructions on submitting a pull request can be found [here](CONTRIBUTING.md).
 
diff --git a/ci/test_filename.py b/ci/test_filename.py
@@ -4,7 +4,7 @@
 # Cartesian product of file names and extensions
 # e.g. README.txt, README.md, CHANGELOG.txt, CHANGELOG.md ...
 file_extensions = ['txt', 'md']
-names = ['README', 'CHANGELOG', 'CONTRIBUTING', 'LICENSE']
+names = ['README', 'CHANGELOG', 'CONTRIBUTING', 'LICENSE', 'CODE_OF_CONDUCT']
 exempt_files = [('.'.join(x)) for x in itertools.product(names, file_extensions)]
 
 def test_filename(md_filepath):

diff --git a/docs/applications/configuration-management/beginners-guide-chef.md b/docs/applications/configuration-management/beginners-guide-chef.md
@@ -14,7 +14,7 @@ title: A Beginner's Guide to Chef
 external_resources:
  - '[Chef](http://www.chef.io)'
  - '[Setting Up a Chef Server, Workstation, and Node on Ubuntu 14.04](/docs/applications/chef/setting-up-chef-ubuntu-14-04)'
- - '[Creating Your First Chef Cookbook](/docs/applications/chef/creating-your-first-chef-cookbook)'
+ - '[Creating Your First Chef Cookbook](/docs/applications/configuration-management/creating-your-first-chef-cookbook/)'
 
 ---
 
@@ -28,7 +28,7 @@ Chef works with three core components: The Chef server, workstations, and nodes.
 
 These three components communicate in a mostly-linear fashion, with any changes being pushed from workstations to the Chef server, and then pulled from the server to the nodes. In turn, information about the node passes to the server to determine which files are different from the current settings and need to be updated.
 
-If you wish to farther explore Chef please see the guides [Setting Up a Chef Server, Workstation, and Node on Ubuntu 14.04](/docs/applications/chef/setting-up-chef-ubuntu-14-04) and [Creating Your First Chef Cookbook](/docs/applications/chef/creating-your-first-chef-cookbook).
+If you wish to farther explore Chef please see the guides [Setting Up a Chef Server, Workstation, and Node on Ubuntu 14.04](/docs/applications/chef/setting-up-chef-ubuntu-14-04) and [Creating Your First Chef Cookbook](/docs/applications/configuration-management/creating-your-first-chef-cookbook/).
 
 ## The Chef Server
 

diff --git a/...ions/configuration-management/learn-how-to-install-ansible-and-run-playbooks.md b/...ions/configuration-management/learn-how-to-install-ansible-and-run-playbooks.md
@@ -22,8 +22,6 @@ external_resources:
 
 ![Ansible](/docs/assets/Learn_How_to_Install_Ansible_and_Run_Playbooks_smg.jpg)
 
-# Getting started with Ansible: An Installation and Configuration Tutorial
-
 Consider the monotony of administering a server fleet; keeping them all updated, pushing changes out to them, copying files, etc. Things can get complicated and time consuming very quickly, but it doesn't have to be that way.
 
 *[Ansible](http://www.ansible.com/home)* is a helpful tool that allows you to create groups of machines, describe how those machines should be configured or what actions should be taken on them, and issue all of these commands from a central location. It uses SSH, so nothing needs to be installed on the machines you are targeting. Ansible only runs on your main control machine, which can even be your laptop! It is a simple solution to a complicated problem.
@@ -40,25 +38,25 @@ Ansible only needs to be installed on the *control machine*, or the machine from
 
 Make sure that you have Python 2.x available on the control machine. Ansible is not compatible with Python 3, nor can you use Windows as the control machine. You can [build Ansible from source](https://github.com/ansible/ansible), or install the latest stable packages using the proper command below.
 
-- Mac OS X:
+### MacOS
 
-      sudo easy_install pip
-      sudo pip install ansible
+    sudo easy_install pip
+    sudo pip install ansible
 
-- CentOS/Fedora:
+### CentOS/Fedora
 
-      sudo yum install ansible
+    sudo yum install ansible
 
-  {{< note >}}
+{{< note >}}
 The EPEL-Release repository may need to be added on certain versions of CentOS, RHEL, and Scientific Linux.
 {{< /note >}}
 
-- Ubuntu:
+### Ubuntu
 
-      sudo apt-get install software-properties-common
-      sudo apt-add-repository ppa:ansible/ansible
-      sudo apt-get update
-      sudo apt-get install ansible
+    sudo apt-get install software-properties-common
+    sudo apt-add-repository ppa:ansible/ansible
+    sudo apt-get update
+    sudo apt-get install ansible
 
 
 ## First Steps to Configuring Ansible
@@ -100,21 +98,18 @@ You executed an Ansible command against one client, but it would be cumbersome t
 1.  By default, the inventory file is expected to be `/etc/ansible/hosts`. Create that path and file if it does not already exist.
 
 
-    {{< note >}}
-If you are running OS X, you may want to create your own Ansible directory elsewhere and then set the path in an Ansible configuration file:
+    If you are running OS X, you may want to create your own Ansible directory elsewhere and then set the path in an Ansible configuration file:
 
-mkdir ~/Path/To/ansible
-touch ~/Path/To/ansible/hosts
-touch ~/.ansible.cfg
+        mkdir ~/Path/To/ansible
+        touch ~/Path/To/ansible/hosts
+        touch ~/.ansible.cfg
 
-Open `~/.ansible.cfg` file and add the following lines:
+    Open `~/.ansible.cfg` file and add the following lines:
 
-{{< file-excerpt "> ~/.ansible.cfg" ini >}}
-[defaults]
-inventory = ~/Path/To/ansible/hosts
-{{< /note >}}
-
-{{< /file-excerpt >}}
+    {{< file-excerpt "~/.ansible.cfg" ini >}}
+    [defaults]
+    inventory = ~/Path/To/ansible/hosts
+    {{< /file-excerpt >}}
 
 
 2.  Add an entry to your hosts file, pointing to a server that you connected to in the previous section.  You can include multiple servers in this file, using either domains or IP addresses, and can even group them: