(doc) fix link in the doc

GitTools · Apr 12, 2017 · e1c7dd6 · e1c7dd6
1 parent 911b48f
commit e1c7dd6
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/docs/why-grm.md b/docs/why-grm.md
@@ -32,8 +32,8 @@ As part of your Release process, you may want to include assets into the GitHub
 
 ## Close Milestone
 
-When working directly in GitHub, publishing a Release doesn't close the associated milestone.  When using the GitReleaseManager's [publish command](commands/publish.md) the associated milestone is also closed.  However, you can also use the [close command](commands/doc:close] directly if you are not using the publish workflow as part of your process.
+When working directly in GitHub, publishing a Release doesn't close the associated milestone.  When using the GitReleaseManager's [publish command](commands/publish.md) the associated milestone is also closed.  However, you can also use the [close command](commands/close.md) directly if you are not using the publish workflow as part of your process.
 
 ## Export Release Notes
 
-When working on a project, you might want to include all the Release Notes within the application itself, let's say in the About dialog.  GitReleaseManager's [export command](commands/export.md) makes it really simple to export the entire history of your application/product, by creating a markdown file with all the information contained in the releases section of GitHub.
+When working on a project, you might want to include all the Release Notes within the application itself, let's say in the About dialog.  GitReleaseManager's [export command](commands/export.md) makes it really simple to export the entire history of your application/product, by creating a markdown file with all the information contained in the releases section of GitHub.