Updated readme

Signed-off-by: Elton Stoneman <elton@sixeyed.com>

Author: sixeyed

README.rst README.mdREADME.rst renamed to README.md

@@ -1,43 +1,41 @@
-Introduction
-=============
+# Image2Docker
 
-`Image2Docker` is a PowerShell module which ports existing Windows application workloads from virtual machines to Docker images. It supports multiple application types, but the initial focus is on IIS. You can use `Image2Docker` to extract ASP.NET websites from a VM, so you can run them in a Docker container with no application changes.
+`Image2Docker` is a PowerShell module which ports existing Windows application workloads from virtual machines to Docker images. It supports multiple application types, but the initial focus is on IIS. You can use `Image2Docker` to extract [ASP.NET websites from a VM](https://blog.docker.com/2016/12/convert-asp-net-web-servers-docker-image2docker/), so you can run them in a Docker container with no application changes.
 
-This project aims to provide a framework to simplify the creation of Dockerfiles for Microsoft Windows Server Hyper-V Container 
+## Introduction
+
+This project aims to provide a framework to simplify the creation of Dockerfiles for Windows Docker
 images, based upon analysis of existing WIM or VHDX image files.
 
-The Microsoft Windows Server 2016 platform introduces new capabilities for containerizing applications. 
+Microsoft Windows 10 and Windows Server  2016 introduce new capabilities for containerizing applications. 
 There are two types of container formats supported on the Microsoft Windows platform:
 
 - **Hyper-V Containers** - Containers with a dedicated kernel and stronger isolation from other containers
-- **Windows Containers** - application isolation using process and namespace isolation, and a shared kernel with the container host
+- **Windows Server Containers** - application isolation using process and namespace isolation, and a shared kernel with the container host
 
-Prerequisites
-=============
+## Prerequisites
 
-Windows Server 2016, or Windows 10 with the Anniversary Update is required on the system that is using this module. 
+Windows Server 2016, or Windows 10 with the Anniversary Update is required to use `Image2Docker`. 
 
-The module generates a [Dockerfile](https://docs.docker.com/engine/reference/builder/) which you can build into a Docker image. The system running the `ConvertTo-Dockerfile` command does not need Docker installed, but you will need [Docker setup on Windows](https://github.com/docker/labs/blob/master/windows/windows-containers/Setup.md) to build images and run containers.
+`Image2Docker` generates a [Dockerfile](https://docs.docker.com/engine/reference/builder/) which you can build into a Docker image. The system running the `ConvertTo-Dockerfile` command does not need Docker installed, but you will need [Docker setup on Windows](https://github.com/docker/labs/blob/master/windows/windows-containers/Setup.md) to build images and run containers.
 
-Installation
-=============
+## Installation
 
 Installing this PowerShell module from the PowerShell Gallery is very easy. Simply invoke ``Install-Module -Name Image2Docker`` in an administrative prompt.
 If you receive any errors, please validate the presence of the ``PowerShellGet`` module by running this command: ``Get-Command -Name PowerShellGet -ListAvailable``.
 You can also validate the presence of the ``Install-Module`` command by running: ``Get-Command -Module PowerShellGet -Name Install-Module``.
 If the ``PowerShellGet`` module or the ``Install-Module`` commands are not accessible, you may not be running a supported version of PowerShell. 
 Make sure that you are running PowerShell 5.0 or later on a Windows 10 client operating system.
 
-Usage
-=============
+## Usage
 
 After installing the ``Image2Docker`` PowerShell module, you will need one or more valid ``.vhdx`` or ``.wim`` files (the "source image").
 To perform a scan of a valid VHDX or WIM image file, simply call the ``ConvertTo-Dockerfile`` command and specify the ``-ImagePath`` parameter, passing in the fully-qualified filesystem path to the source image.
 
-::
-
-  ### Perform scan of Windows source image
+```PowerShell
+  # Perform scan of Windows source image
   ConvertTo-Dockerfile -ImagePath c:\docker\myimage.wim
+```
 
 To improve performance of the image scan, you may also specify the artifacts that will be discovered within the image.
 This avoids the performance hit by preventing scanning for artifacts that are intentionally excluded from the scanning process.
@@ -46,19 +44,27 @@ Once you have identified one or more artifacts that you would like to scan for,
 
 Example:  
 
-::
-
-  ### List out supported artifacts
+```PowerShell
+  # List out supported artifacts
   Get-WindowsArtifact
 
-  ### Perform scan and Dockerfile generation
+  # Perform scan and Dockerfile generation
   ConvertTo-Dockerfile -ImagePath c:\docker\myimage.vhdx -Artifact IIS, Apache
 
-  ### Extract a single wesbite from an IIS virtual machine
+  # Extract a single wesbite from an IIS virtual machine
   ConvertTo-Dockerfile -ImagePath c:\vms\iis.vhd -Artifact IIS -ArtifactParam aspnet-webapi
+```
 
-Artifacts
-=============
+To generate Dockerfile from a VHD, build a Docker image and run a container:
+
+```PowerShell
+  ConvertTo-Dockerfile -ImagePath c:\vms\iis.vhd -Artifact IIS -ArtifactParam aspnet-webapi -OutputPath c:\i2d2
+  cd c:\i2d2
+  docker build -t aspnet-webapi .
+  docker run -d -p 80:80 aspnet-webapi
+```
+
+## Artifacts
 
 This project supports discovery of custom artifacts.
 Each artifact is represented by a folder that is contained within the ``.\Functions\Private\Artifacts`` subdirectory, containing at least two PowerShell script files that contain :
@@ -72,8 +78,7 @@ You can also include any files within the Artifact directory that may be used to
 
 You can add your own discovery artifacts to this project, by issuing a pull request. If you don't wish to share the artifacts publicly, you can simply place them into the module's ``.\Functions\Private\Artifacts`` directory on each system that will perform image scans.
 
-Supported Artifacts
-===================
+## Supported Artifacts
 
 This project currently supports discovery of the following artifacts:
 
@@ -87,8 +92,8 @@ This project currently supports discovery of the following artifacts:
 - Microsoft SQL Server instances
 - Apache Web Server
 
-Known Issues
-=============
+
+### Known Issues
 
 1. Dism Error: 0x8000000a 
 ------------------------------------