From ddf8b7bc32c52ff89298a15e1ae7b86b5d97c97b Mon Sep 17 00:00:00 2001
From: Kris De Volder <kdevolder@pivotal.io>
Date: Mon, 19 Dec 2016 11:29:11 -0800
Subject: [PATCH] Some cleanups to vscode-manifest-yaml packaging

---
 .../vscode-manifest-yaml/package.json         |  4 +--
 .../vsc-extension-quickstart.md               | 33 -------------------
 2 files changed, 2 insertions(+), 35 deletions(-)
 delete mode 100644 vscode-extensions/vscode-manifest-yaml/vsc-extension-quickstart.md

diff --git a/vscode-extensions/vscode-manifest-yaml/package.json b/vscode-extensions/vscode-manifest-yaml/package.json
index 2f786484a..7c6c54a45 100644
--- a/vscode-extensions/vscode-manifest-yaml/package.json
+++ b/vscode-extensions/vscode-manifest-yaml/package.json
@@ -1,13 +1,13 @@
 {
   "name": "vscode-manifest-yaml",
   "displayName": "Cloudfoundry Manifest YML Support",
-  "description": "Adds linting, content assist and hoverinfo's for Cloudfoundry Deployment Manifests (a.k.a. `manifest.yml` files.",
+  "description": "Adds linting, content assist and hoverinfo's for Cloudfoundry Deployment Manifests (a.k.a. `manifest.yml`) files.",
   "icon": "icon.png",
   "version": "0.0.1",
   "publisher": "Pivotal",
   "repository": {
     "type": "git",
-    "url": "https://github.com/kdvolder/vscode-lsapi-example.git"
+    "url": "https://github.com/spring-projects/sts4.git"
   },
   "license": "EPL-1.0",
   "engines": {
diff --git a/vscode-extensions/vscode-manifest-yaml/vsc-extension-quickstart.md b/vscode-extensions/vscode-manifest-yaml/vsc-extension-quickstart.md
deleted file mode 100644
index 4dfd9da2d..000000000
--- a/vscode-extensions/vscode-manifest-yaml/vsc-extension-quickstart.md
+++ /dev/null
@@ -1,33 +0,0 @@
-# Welcome to your first VS Code Extension
-
-## What's in the folder
-* This folder contains all of the files necessary for your extension
-* `package.json` - this is the manifest file in which you declare your extension and command. 
-The sample plugin registers a command and defines its title and command name. With this information 
-VS Code can show the command in the command palette. It doesn’t yet need to load the plugin. 
-* `src/extension.ts` - this is the main file where you will provide the implementation of your command. 
-The file exports one function, `activate`, which is called the very first time your extension is 
-activated (in this case by executing the command). Inside the `activate` function we call `registerCommand`. 
-We pass the function containing the implementation of the command as the second parameter to 
-`registerCommand`.
-
-## Get up and running straight away 
-* press `F5` to open a new window with your extension loaded
-* run your command from the command palette by pressing (`Ctrl+Shift+P` or `Cmd+Shift+P` on Mac) and typing `Hello World`
-* set breakpoints in your code inside `src/extension.ts` to debug your extension
-* find output from your extension in the debug console
-
-## Make changes
-* you can relaunch the extension from the debug toolbar after changing code in `src/extension.ts`
-* you can also reload (`Ctrl+R` or `Cmd+R` on Mac) the VS Code window with your extension to load your changes
-
-## Explore the API
-* you can open the full set of our API when you open the file `node_modules/vscode/vscode.d.ts`
-
-## Run tests
-* open the debug viewlet (`Ctrl+Shift+D` or `Cmd+Shift+D` on Mac) and from the launch configuration dropdown pick `Launch Tests`
-* press `F5` to run the tests in a new window with your extension loaded
-* see the output of the test result in the debug console
-* make changes to `test/extension.test.ts` or create new test files inside the `test` folder
-	* by convention, the test runner will only consider files matching the name pattern `**.test.ts`
-	* you can create folders inside the `test` folder to structure your tests any way you want
\ No newline at end of file