Clean up inconsistent and erroneous ms.dates

kraigb · kraigb · commit eab560433a66 · 2019-04-08T15:33:49.000-07:00
diff --git a/articles/azure-functions/functions-test-a-function.md b/articles/azure-functions/functions-test-a-function.md
@@ -10,7 +10,7 @@ keywords: azure functions, functions, event processing, webhooks, dynamic comput
 ms.service: azure-functions
 ms.devlang: multiple
 ms.topic: conceptual
-ms.date: 030/25/2019
+ms.date: 03/25/2019
 ms.author: cshoe
 ---
 
diff --git a/articles/dev-spaces/get-started-java.md b/articles/dev-spaces/get-started-java.md
@@ -5,7 +5,7 @@ services: azure-dev-spaces
 ms.service: azure-dev-spaces
 author: "stepro"
 ms.author: "stephpr"
-ms.date: "09/26/2018"
+ms.date: 09/26/2018
 ms.topic: "tutorial"
 description: "Rapid Kubernetes development with containers and microservices on Azure"
 keywords: "Docker, Kubernetes, Azure, AKS, Azure Kubernetes Service, containers, Helm, service mesh, service mesh routing, kubectl, k8s"
diff --git a/articles/dev-spaces/get-started-netcore-visualstudio.md b/articles/dev-spaces/get-started-netcore-visualstudio.md
@@ -7,7 +7,7 @@ ms.custom: vs-azure
 ms.workload: azure-vs
 author: zr-msft
 ms.author: zarhoads
-ms.date: "07/09/2018"
+ms.date: 07/09/2018
 ms.topic: "tutorial"
 description: "Rapid Kubernetes development with containers and microservices on Azure"
 keywords: "Docker, Kubernetes, Azure, AKS, Azure Kubernetes Service, containers, Helm, service mesh, service mesh routing, kubectl, k8s"
diff --git a/articles/dev-spaces/get-started-netcore.md b/articles/dev-spaces/get-started-netcore.md
@@ -5,7 +5,7 @@ services: azure-dev-spaces
 ms.service: azure-dev-spaces
 author: zr-msft
 ms.author: zarhoads
-ms.date: "09/26/2018"
+ms.date: 09/26/2018
 ms.topic: "tutorial"
 description: "Rapid Kubernetes development with containers and microservices on Azure"
 keywords: "Docker, Kubernetes, Azure, AKS, Azure Kubernetes Service, containers, Helm, service mesh, service mesh routing, kubectl, k8s"
diff --git a/articles/dev-spaces/get-started-nodejs.md b/articles/dev-spaces/get-started-nodejs.md
@@ -5,7 +5,7 @@ services: azure-dev-spaces
 ms.service: azure-dev-spaces
 author: zr-msft
 ms.author: zarhoads
-ms.date: "09/26/2018"
+ms.date: 09/26/2018
 ms.topic: "tutorial"
 description: "Rapid Kubernetes development with containers and microservices on Azure"
 keywords: "Docker, Kubernetes, Azure, AKS, Azure Kubernetes Service, containers, Helm, service mesh, service mesh routing, kubectl, k8s"
diff --git a/articles/dev-spaces/how-dev-spaces-works.md b/articles/dev-spaces/how-dev-spaces-works.md
@@ -6,7 +6,7 @@ ms.service: azure-dev-spaces
 ms.component: azds-kubernetes
 author: zr-msft
 ms.author: zarhoads
-ms.date: "03/04/2019"
+ms.date: 03/04/2019
 ms.topic: "conceptual"
 description: "Describes the processes that power Azure Dev Spaces and how they are configured in the azds.yaml configuration file"
 keywords: "azds.yaml, Azure Dev Spaces, Dev Spaces, Docker, Kubernetes, Azure, AKS, Azure Kubernetes Service, containers"
diff --git a/articles/dev-spaces/multi-service-java.md b/articles/dev-spaces/multi-service-java.md
@@ -5,7 +5,7 @@ services: azure-dev-spaces
 ms.service: azure-dev-spaces
 author: DrEsteban
 ms.author: stevenry
-ms.date: "11/21/2018"
+ms.date: 11/21/2018
 ms.topic: "tutorial"
 description: "Rapid Kubernetes development with containers and microservices on Azure"
 keywords: "Docker, Kubernetes, Azure, AKS, Azure Kubernetes Service, containers, Helm, service mesh, service mesh routing, kubectl, k8s "
@@ -101,4 +101,4 @@ You now have a multi-container application where each container can be developed
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Learn about team development in Dev Spaces](team-development-java.md)
+> [Learn about team development in Dev Spaces](team-development-java.md)
diff --git a/articles/dev-spaces/multi-service-netcore-visualstudio.md b/articles/dev-spaces/multi-service-netcore-visualstudio.md
@@ -7,7 +7,7 @@ ms.custom: vs-azure
 ms.workload: azure-vs
 author: zr-msft
 ms.author: zarhoads
-ms.date: "07/09/2018"
+ms.date: 07/09/2018
 ms.topic: "tutorial"
 description: "Rapid Kubernetes development with containers and microservices on Azure"
 keywords: "Docker, Kubernetes, Azure, AKS, Azure Kubernetes Service, containers, Helm, service mesh, service mesh routing, kubectl, k8s "
@@ -107,4 +107,4 @@ You now have a multi-container application where each container can be developed
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Learn about team development in Dev Spaces](team-development-netcore-visualstudio.md)
+> [Learn about team development in Dev Spaces](team-development-netcore-visualstudio.md)
diff --git a/articles/dev-spaces/multi-service-netcore.md b/articles/dev-spaces/multi-service-netcore.md
@@ -5,7 +5,7 @@ services: azure-dev-spaces
 ms.service: azure-dev-spaces
 author: DrEsteban
 ms.author: stevenry
-ms.date: "11/21/2018"
+ms.date: 11/21/2018
 ms.topic: "tutorial"
 description: "Rapid Kubernetes development with containers and microservices on Azure"
 keywords: "Docker, Kubernetes, Azure, AKS, Azure Kubernetes Service, containers, Helm, service mesh, service mesh routing, kubectl, k8s "
@@ -104,4 +104,4 @@ You now have a multi-container application where each container can be developed
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Learn about team development in Dev Spaces](team-development-netcore.md)
+> [Learn about team development in Dev Spaces](team-development-netcore.md)
diff --git a/articles/dev-spaces/multi-service-nodejs.md b/articles/dev-spaces/multi-service-nodejs.md
@@ -5,7 +5,7 @@ services: azure-dev-spaces
 ms.service: azure-dev-spaces
 author: DrEsteban
 ms.author: stevenry
-ms.date: "11/21/2018"
+ms.date: 11/21/2018
 ms.topic: "tutorial"
 description: "Rapid Kubernetes development with containers and microservices on Azure"
 keywords: "Docker, Kubernetes, Azure, AKS, Azure Kubernetes Service, containers, Helm, service mesh, service mesh routing, kubectl, k8s "
@@ -95,4 +95,4 @@ You now have a multi-container application where each container can be developed
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Learn about team development in Dev Spaces](team-development-nodejs.md)
+> [Learn about team development in Dev Spaces](team-development-nodejs.md)
diff --git a/articles/dev-spaces/quickstart-java.md b/articles/dev-spaces/quickstart-java.md
@@ -6,7 +6,7 @@ services: azure-dev-spaces
 ms.service: azure-dev-spaces
 ms.subservice: azds-kubernetes
 ms.author: zarhoads
-ms.date: "03/22/2019"
+ms.date: 03/22/2019
 ms.topic: "quickstart"
 description: "Rapid Kubernetes development with containers, microservices, and Java on Azure"
 keywords: "Docker, Kubernetes, Azure, AKS, Azure Kubernetes Service, containers, Java, Helm, service mesh, service mesh routing, kubectl, k8s"
diff --git a/articles/dev-spaces/quickstart-netcore-visualstudio.md b/articles/dev-spaces/quickstart-netcore-visualstudio.md
@@ -6,7 +6,7 @@ services: azure-dev-spaces
 ms.service: azure-dev-spaces
 ms.subservice: azds-kubernetes
 ms.author: zarhoads
-ms.date: "03/22/2019"
+ms.date: 03/22/2019
 ms.topic: "quickstart"
 description: "Rapid Kubernetes development with containers and microservices on Azure"
 keywords: "Docker, Kubernetes, Azure, AKS, Azure Kubernetes Service, containers, Helm, service mesh, service mesh routing, kubectl, k8s"
diff --git a/articles/dev-spaces/quickstart-netcore.md b/articles/dev-spaces/quickstart-netcore.md
@@ -6,7 +6,7 @@ services: azure-dev-spaces
 ms.service: azure-dev-spaces
 ms.subservice: azds-kubernetes
 ms.author: zarhoads
-ms.date: "03/22/2019"
+ms.date: 03/22/2019
 ms.topic: "quickstart"
 description: "Rapid Kubernetes development with containers and microservices on Azure"
 keywords: "Docker, Kubernetes, Azure, AKS, Azure Kubernetes Service, containers, Helm, service mesh, service mesh routing, kubectl, k8s"
diff --git a/articles/dev-spaces/quickstart-nodejs.md b/articles/dev-spaces/quickstart-nodejs.md
@@ -6,7 +6,7 @@ services: azure-dev-spaces
 ms.service: azure-dev-spaces
 ms.subservice: azds-kubernetes
 ms.author: zarhoads
-ms.date: "03/22/2019"
+ms.date: 03/22/2019
 ms.topic: "quickstart"
 description: "Rapid Kubernetes development with containers, microservices, and Node.js on Azure"
 keywords: "Docker, Kubernetes, Azure, AKS, Azure Kubernetes Service, containers, Helm, service mesh, service mesh routing, kubectl, k8s"
@@ -204,4 +204,4 @@ az group delete --name MyResourceGroup --yes --no-wait
 Learn how Azure Dev Spaces helps you develop more complex applications across multiple containers, and how you can simplify collaborative development by working with different versions or branches of your code in different spaces.
 
 > [!div class="nextstepaction"]
-> [Working with multiple containers and team development](multi-service-nodejs.md)
+> [Working with multiple containers and team development](multi-service-nodejs.md)
diff --git a/articles/dev-spaces/team-development-java.md b/articles/dev-spaces/team-development-java.md
@@ -5,7 +5,7 @@ services: azure-dev-spaces
 ms.service: azure-dev-spaces
 author: "stepro"
 ms.author: "stephpr"
-ms.date: "08/01/2018"
+ms.date: 08/01/2018
 ms.topic: "tutorial"
 description: "Rapid Kubernetes development with containers and microservices on Azure"
 keywords: "Docker, Kubernetes, Azure, AKS, Azure Kubernetes Service, containers, Helm, service mesh, service mesh routing, kubectl, k8s "
diff --git a/articles/dev-spaces/team-development-netcore-visualstudio.md b/articles/dev-spaces/team-development-netcore-visualstudio.md
@@ -7,7 +7,7 @@ ms.custom: vs-azure
 ms.workload: azure-vs
 author: DrEsteban
 ms.author: stevenry
-ms.date: "12/09/2018"
+ms.date: 12/09/2018
 ms.topic: "tutorial"
 description: "Rapid Kubernetes development with containers and microservices on Azure"
 keywords: "Docker, Kubernetes, Azure, AKS, Azure Kubernetes Service, containers, Helm, service mesh, service mesh routing, kubectl, k8s "
@@ -146,4 +146,4 @@ The following example lists the Azure Dev Spaces controllers in your active subs
 ```cmd
     azds controller list
     az aks remove-dev-spaces --name myaks --resource-group myaks-rg
-```
+```
diff --git a/articles/dev-spaces/team-development-netcore.md b/articles/dev-spaces/team-development-netcore.md
@@ -5,7 +5,7 @@ services: azure-dev-spaces
 ms.service: azure-dev-spaces
 author: zr-msft
 ms.author: zarhoads
-ms.date: "07/09/2018"
+ms.date: 07/09/2018
 ms.topic: "tutorial"
 description: "Rapid Kubernetes development with containers and microservices on Azure"
 keywords: "Docker, Kubernetes, Azure, AKS, Azure Kubernetes Service, containers, Helm, service mesh, service mesh routing, kubectl, k8s "
diff --git a/articles/dev-spaces/team-development-nodejs.md b/articles/dev-spaces/team-development-nodejs.md
@@ -5,7 +5,7 @@ services: azure-dev-spaces
 ms.service: azure-dev-spaces
 author: zr-msft
 ms.author: zarhoads
-ms.date: "07/09/2018"
+ms.date: 07/09/2018
 ms.topic: "tutorial"
 description: "Rapid Kubernetes development with containers and microservices on Azure"
 keywords: "Docker, Kubernetes, Azure, AKS, Azure Kubernetes Service, containers, Helm, service mesh, service mesh routing, kubectl, k8s "
diff --git a/articles/dev-spaces/troubleshooting.md b/articles/dev-spaces/troubleshooting.md
@@ -5,7 +5,7 @@ services: azure-dev-spaces
 ms.service: azure-dev-spaces
 author: zr-msft
 ms.author: zarhoads
-ms.date: "09/11/2018"
+ms.date: 09/11/2018
 ms.topic: "conceptual"
 description: "Rapid Kubernetes development with containers and microservices on Azure"
 keywords: "Docker, Kubernetes, Azure, AKS, Azure Kubernetes Service, containers, Helm, service mesh, service mesh routing, kubectl, k8s "
@@ -318,4 +318,4 @@ configurations:
 The node running the pod with the Node.js application you are trying to attach to with a debugger has exceeded the *fs.inotify.max_user_watches* value. In some cases, [the default value of *fs.inotify.max_user_watches* may be too small to handle attaching a debugger directly to a pod](https://github.com/Azure/AKS/issues/772).
 
 ### Try
-A temporary workaround for this issue is to increase the value of *fs.inotify.max_user_watches* on each node in the cluster and restart that node for the changes to take effect.
+A temporary workaround for this issue is to increase the value of *fs.inotify.max_user_watches* on each node in the cluster and restart that node for the changes to take effect.
