From cd157aca783bcf22f441e8e65c0890ac72edd7cc Mon Sep 17 00:00:00 2001
From: daviddreher2 <30770928+daviddreher2@users.noreply.github.com>
Date: Wed, 17 Oct 2018 18:58:19 +0800
Subject: [PATCH] Update README.md

fixed some spelling and grammar
---
 docs/debugging/README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/debugging/README.md b/docs/debugging/README.md
index fb074aa7881..760f2ef9355 100644
--- a/docs/debugging/README.md
+++ b/docs/debugging/README.md
@@ -19,7 +19,7 @@ You can do this in Bash with `export PATH=$PATH:$HOME/.dotnet` or in PowerShell
 
 Once the extension is installed, you have to open a C# file to force VS Code to
 install the actual .NET Core debugger (the editor will tell you to do this if
-you attempt to debug and haven't already open a C# file).
+you attempt to debug and haven't already opened a C# file).
 
 The committed `.vscode` folder in the root of this repository contains
 the `launch.json` and `tasks.json` files which provide Core PowerShell
@@ -39,7 +39,7 @@ launch an external console with PowerShell running interactively. If neither of
 these installed, the editor will tell you to do so.
 
 Alternatively, the ".NET Core Attach" configuration will start listening for a
-process named `powershell`, and will attach to it. If you need more fine grained
+process named `powershell`, and will attach to it. If you need more fine-grained
 control, replace `processName` with `processId` and provide a PID. (Please be
 careful not to commit such a change.)