Skip to content

Commit e1c7dd6

Browse files
authored
(doc) fix link in the doc
1 parent 911b48f commit e1c7dd6

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/why-grm.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -32,8 +32,8 @@ As part of your Release process, you may want to include assets into the GitHub
3232

3333
## Close Milestone
3434

35-
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.
35+
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.
3636

3737
## Export Release Notes
3838

39-
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.
39+
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.

0 commit comments

Comments
 (0)