move oci layout listing

Signed-off-by: Michael McCracken <mikmccra@cisco.com>

doc/talks/stacker101/stacker101.md

@@ -141,24 +141,6 @@ Build, Distribute and Run software as containers
 Sounds a bit like "docker build," right?
 
 
----
-
-# OCI layouts: what exactly are we building?
-
-```
- tree -h mylayout
-[4.0K]  mylayout
-├── [4.0K]  blobs
-│   └── [4.0K]  sha256
-│       ├── [ 82M]  1377df6593e020... # first layer of base image           <──┐
-│       ├── [1.9M]  27ac08e0731341... # top layer of base image we imported <──┤
-│       ├── [ 142]  5aa530963e08fc... # layer added during build            <──┤
-│       ├── [1.0K]  eea0dfeb15fd39... # image manifest        ──>┐          ──>┘ <─┐
-│       └── [ 988]  fb47d876bd9bc6... # config blob for image <──┘                 │
-├── [ 301]  index.json                # index with tag "test" for image "eea0d" ──>┘
-└── [  31]  oci-layout
-```
-
 ---
 
 # How is it different?
@@ -196,16 +178,34 @@ instead of waiting for consensus and full cross platform support -->
 
 ---
 
-# `stacker build -f my.stacker.yaml`
 
 ![](overview.png)
 
-<!-- 
 
-get a base image, import files, start a container, save changes -->
+---
+
+
+# OCI layouts: what exactly are we building?
+
+An OCI Layout with one image tagged "test":
+
+```
+% tree -h mylayout
+[4.0K]  mylayout
+├── [4.0K]  blobs
+│   └── [4.0K]  sha256
+│       ├── [ 82M]  1377df6593e020... # first layer of base image           <──┐
+│       ├── [1.9M]  27ac08e0731341... # top layer of base image we imported <──┤
+│       ├── [ 142]  5aa530963e08fc... # layer added during build            <──┤
+│       ├── [1.0K]  eea0dfeb15fd39... # image manifest        ──>┐          ──>┘ <─┐
+│       └── [ 988]  fb47d876bd9bc6... # config blob for image <──┘                 │
+├── [ 301]  index.json                # index with tag "test" for image "eea0d" ──>┘
+└── [  31]  oci-layout
+```
 
 ---
 
+
 # get a base image: from a registry
 
 ```yaml
@@ -267,7 +267,6 @@ A script that runs in the container you have set up.
 bat -n --decorations always 2.stacker.yaml
 ```
 
-2.stacker.yaml
 
 changes made to most files (except those under `/stacker`) are persisted in the final container image.
 
@@ -282,21 +281,6 @@ STYLE NOTE - yaml multiline string is best -->
 
 ---
 
-Alternate syntax:
-
-```yaml
-myimage:
-  from: ...
-  run:
-    - echo "hacking is" > /fun
-    - gzip fun
-```
-
-<!-- 
-
-you can also use a list of strings like this but it is not as clear and can get confused with Makefile recipe syntax -->
-
----
 
 # Imports with no dest and no hash