From 48e023b342aa74ea262fbbab3a69945205d1c04b Mon Sep 17 00:00:00 2001
From: "Brian Moore (AZURE RESOURCE MANAGER)" <bmoore@microsoft.com>
Date: Tue, 26 Feb 2019 18:42:34 -0600
Subject: [PATCH] bp guide update

---
 1-CONTRIBUTION-GUIDE/best-practices.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/1-CONTRIBUTION-GUIDE/best-practices.md b/1-CONTRIBUTION-GUIDE/best-practices.md
index 7aa8b207ce04..75c63e2bc08a 100644
--- a/1-CONTRIBUTION-GUIDE/best-practices.md
+++ b/1-CONTRIBUTION-GUIDE/best-practices.md
@@ -92,11 +92,13 @@ The common properties should be authored consistently to provide for understanda
 ```json
     "resources": [
         {
+            "comments": "if any",
             "condition": true,
             "type": "Microsoft.Compute/virtualMachines",
             "apiVersion": "2017-12-01",
             "name": "[concat(parameters('virtualMachineName'), copyIndex(1))]",
             "location": "[parameters('location')]",
+            "sku": {},
             "copy": {
                 "name": "vmLoop",
                 "count": "[parameters('numberOfVMs')]"
@@ -104,8 +106,8 @@ The common properties should be authored consistently to provide for understanda
             "dependsOn": [
                 "nicLoop"
             ],
-            "comments": "this is the vm loop",
-            "properties": {
+            "tags": {},
+            "properties": {}
 ```
 ### dependsOn  
 Deployment sequence dependencies can be specified by using the dependsOn property.  Dependencies are only allowed for resources that are deployed within the same template. They are not needed for existing resources, and for nested deployments, the dependency is created on the deployment resource itself.