bundle: Transition from Markdown to AsciiDoc

This gets a title [1] with an anchor [2], and the old *...* becomes
_..._ [3].  I've also dropped the separate "Container Format" header
because it didn't seem to be adding any useful information.

[1]: http://asciidoc.org/userguide.html#X17
     Titles
[2]: http://asciidoc.org/userguide.html#X30
     anchor
[3]: http://asciidoc.org/userguide.html#X51
     10.1. Quoted Text

Signed-off-by: W. Trevor King <[email protected]>

Author: wking

bundle.md renamed to bundle.asc

@@ -1,22 +1,24 @@
-# Filesystem Bundle
+[[bundle,bundle]]
+Filesystem Bundle
+-----------------
 
-## Container Format
+:os-x-bundle: http://en.wikipedia.org/wiki/Bundle_%28OS_X%29
 
-This section defines a format for encoding a container as a *filesystem bundle* - a set of files organized in a certain way, and containing all the necessary data and metadata for any compliant runtime to perform all standard operations against it.
-See also [OS X application bundles](http://en.wikipedia.org/wiki/Bundle_%28OS_X%29) for a similar use of the term *bundle*.
+This section defines a format for encoding a container as a _filesystem bundle_ - a set of files organized in a certain way, and containing all the necessary data and metadata for any compliant runtime to perform all standard operations against it.
+See also {os-x-bundle}[OS X application bundles] for a similar use of the term _bundle_.
 
 The definition of a bundle is only concerned with how a container, and its configuration data, are stored on a local filesystem so that it can be consumed by a compliant runtime.
 
 A Standard Container bundle contains all the information needed to load and run a container.
 This MUST include the following artifacts:
 
 1. `config.json`: contains configuration data.
-This REQUIRED file MUST reside in the root of the bundle directory and MUST be named `config.json`.
-See [`config.json`](config.md) for more details.
+   This REQUIRED file MUST reside in the root of the bundle directory and MUST be named `config.json`.
+   See `<<config>>` for more details.
 
 2. A directory representing the root filesystem of the container.
-While the name of this REQUIRED directory may be arbitrary, users should consider using a conventional name, such as `rootfs`.
-This directory MUST be referenced from within the `config.json` file.
+   While the name of this REQUIRED directory may be arbitrary, users should consider using a conventional name, such as `rootfs`.
+   This directory MUST be referenced from within the `config.json` file.
 
 While these artifacts MUST all be present in a single directory on the local filesystem, that directory itself is not part of the bundle.
-In other words, a tar archive of a *bundle* will have these artifacts at the root of the archive, not nested within a top-level directory.
+In other words, a tar archive of a _bundle_ will have these artifacts at the root of the archive, not nested within a top-level directory.

oci-runtime-spec.asc

@@ -17,3 +17,5 @@ include::use-cases.asc[]
 include::definitions.asc[]
 
 include::protocols.asc[]
+
+include::bundle.asc[]

use-cases.asc

@@ -6,7 +6,7 @@ To provide context for users the following section gives example use cases for e
 Application Bundle Builders
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Application bundle builders can create a `<<bundle>>` directory that includes all of the files required for launching an application as a container.
+Application bundle builders can create a <<bundle>> directory that includes all of the files required for launching an application as a container.
 The bundle contains an OCI `<<config>>` where the builder can specify host-independent details such as `<<process.args,which executable to launch>>` and host-specific settings such as `<<mounts>>`, `<<hooks>>`, `<<linux-namespaces>>` and `<<cgroups>>`.
 Because the configuration includes host-specific settings, application bundle directories copied between two hosts may require configuration adjustments.