Updating Docker.DotNet submodule to track ahmetalpbalkan master.

Signed-off-by: Stefan J. Wernli <swernli@microsoft.com>

.gitmodules

@@ -1,3 +1,4 @@
 [submodule "src/Docker.DotNet"]
 	path = src/Docker.DotNet
-	url = https://github.com/swernli/Docker.DotNet.git
+	url = https://github.com/ahmetalpbalkan/Docker.DotNet.git
+	branch = master

README.md

@@ -1,9 +1,9 @@
-#PowerShell for Docker
+# PowerShell for Docker
 The goal of this project is to create a PowerShell module for the [Docker Engine]( https://github.com/docker/docker/), which can be utilized as an alternative or in conjunction with the Docker client (CLI).
-##Current version
+## Current version
   0.1.0-alpha (pre-release)
 
-##Requirements and Goals
+## Requirements and Goals
 ### Requirements
 1.	Must follow the Docker Remote API interop and breaking change policy (https://docs.docker.com/engine/breaking_changes/)
 2.	Must work locally or remotely, with remote following appropriate authentication and security mechanisms (i.e. TLS).
@@ -23,17 +23,18 @@ The goal of this project is to create a PowerShell module for the [Docker Engine
 * https://blogs.msdn.microsoft.com/dotnet/2016/02/10/porting-to-net-core/
 * https://technet.microsoft.com/en-us/library/hh849695.aspx
 
-##Compilation
-To compile this project, use the dotnet CLI (https://github.com/dotnet/cli) to execute a publish command:
-
+## Compilation
+To compile this project, use the dotnet CLI (https://github.com/dotnet/cli) to execute a restore command followed by a publish command:
+"dotnet restore"
 "dotnet publish .\\src\\Docker.PowerShell -o .\\src\\Docker.PowerShell\\bin\\Module\\Docker.PowerShell -r win"
 
 This will produce the PowerShell module  at ".\src\Docker.PowerShell\bin\Module\Docker.PowerShell" in the project folder.  If Visual Studio is not already installed, the dotnet CLI may require an additional installation of the .NET 4.6 developer pack (https://www.microsoft.com/en-us/download/details.aspx?id=48136).
 
-NOTE: This project uses Docker.DotNet as a git submodule (use "git submodule --help" to view manual pages for submodule).  This requires one-time initializtion of the submodule with "git submodule init" and updating via "git submodule update" whenever the proejct targets a new commit of Docker.DotNet.
+### Git submodules for Docker.DotNet
+This project uses Docker.DotNet as a git submodule ("git submodule --help" to view manual pages for submodule).  When first starting a new clone of Docker.Powershell, this requires one-time initializtion of the submodule with "git submodule init" to prepare the directories used by the submodule. Then, use "git submodule update" to pull down the latest commit of Docker.DotNet that is associated with the current branch of Docker.PowerShell.  When making changes to Docker.PowerShell that use corresponding changes made to Docker.DotNet master branch, use "git submodule update --remote" to sync the submodule to the latest in master, and include the updated commit id for the submodule in the changes submitted to Docker.Powershell.
 
-##Using Visual Studio Code
+## Using Visual Studio Code
 This project also includes support for Visual Studio Code (https://code.visualstudio.com/, https://github.com/Microsoft/vscode) in the .vscode folder.  Using VSCode on the top-level folder, the restore, build, and test tasks will be available.  Restore will perform "dotnet restore" across the whole project to reload any dependencies. Build will perform the "dotnet publish" command with the arguments listed in the compilation section above.  Test will launch a new powershell window with the module loaded for manual testing.
 
-##High Level Design
+## High Level Design
 The PowerShell module for Docker is built on top of the Docker Engine REST Interface (https://docs.docker.com/engine/reference/api/docker_remote_api/).

src/Docker.DotNet

@@ -1 +1 @@
-Subproject commit e192a1044e78b500564a448edbbe25d0dc9717f2
+Subproject commit e0abd0bfb724ef8f69e9ac0b5d50f5ac989d49cc