From f0bb65979475c139096cc24b0fafaebd524dae4f Mon Sep 17 00:00:00 2001
From: David Fowler <davidfowl@gmail.com>
Date: Thu, 2 Apr 2020 21:59:04 -0700
Subject: [PATCH] Update schema.md

---
 docs/schema.md | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/docs/schema.md b/docs/schema.md
index d2b6c751..16e50982 100644
--- a/docs/schema.md
+++ b/docs/schema.md
@@ -209,8 +209,8 @@ Bindings represent protocols *exposed* by a service. How bindings are specified
 Bindings should either provide:
 
 - A `connectionString`
-- A `protocol` and `port`
-- A `protocol` and `autoAssignPort: true`
+- A `protocol`
+- A `port`
 
 ### Binding Example
 
@@ -259,7 +259,7 @@ Specifies the port used by the binding when running in a docker container.
 
 Specifies the port used by the binding when running in a docker container.
 
-#### `autoAssignPort` (bool)
+#### `autoAssignPort` (bool deprecated, by default a port will be auto assigned if no connection string was specified)
 
 Specifies that the port should be assigned randomly. Defaults to `false`. This is currently only useful for projects - where the tye host will automatically infer bindings with `autoAssignPort: true`
 
@@ -282,10 +282,14 @@ name: myapplication
 
 ### Volume Properties
 
-#### `source` (string) *required*
+#### `source` (string)
 
 The local path.
 
+### `name` (string)
+
+A named docker volume.
+
 #### `target` (string) *required*
 
 The destination path within the container.