Return Markdown files to /docs directory

Signed-off-by: Luc Perkins <lucperkins@gmail.com>

docs/client-opts.md

@@ -1,7 +1,4 @@
----
-title: Client options
-draft: true
----
+# Client options
 
 The containerd client was built to be easily extended by consumers.
 The goal is that the execution flow of the calls remain the same across implementations while `Opts` are written to extend functionality.

docs/dockercon-summit.md

@@ -1,8 +1,3 @@
----
-title: Dockercon 2017 Summit
-draft: true
----
-
 # Dockercon 2017 Summit
 
 This year at Dockercon US 2017 we will be having a containerd Summit on Thursday morning the week of the conference.

docs/getting-started.md

@@ -1,7 +1,4 @@
----
-title: Getting started with containerd
-draft: true
----
+# Getting started with containerd
 
 There are many different ways to use containerd.
 If you are a developer working on containerd you can use the `ctr` tool to quickly test features and functionality without writing extra code.

docs/namespaces.md

@@ -1,7 +1,4 @@
----
-title: containerd Namespaces and Multi-Tenancy
-draft: true
----
+# containerd Namespaces and Multi-Tenancy
 
 containerd offers a fully namespaced API so multiple consumers can all use a single containerd instance without conflicting with one another.
 Namespaces allow multi-tenancy within a single daemon. This removes the need for the common pattern of using nested containers to achieve this separation.

docs/ops.md

@@ -1,7 +1,4 @@
----
-title: containerd for Ops and Admins
-draft: true
----
+# containerd for Ops and Admins
 
 containerd is meant to be a simple daemon to run on any system.
 It provides a minimal config with knobs to configure the daemon and what plugins are used when necessary.