From af82cf7940e7aaf9b8e2bc673dbad7d6f13053b5 Mon Sep 17 00:00:00 2001 From: Enrico Sada Date: Thu, 17 Dec 2015 15:16:29 +0100 Subject: [PATCH] typo --- Documentation/developer-guide.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/developer-guide.md b/Documentation/developer-guide.md index 58eb4e969..a83a7aeb9 100644 --- a/Documentation/developer-guide.md +++ b/Documentation/developer-guide.md @@ -37,7 +37,7 @@ In order to build .NET Command Line Interface, you need the following installed ##Adding a Command -The donet CLI considers any executable on the path named `dotnet-{commandName}` to be a command it can call out to. `dotnet publish`, for example, is added to the path as an executable called `dotnet-publish`. To add a new command we must create the executable and then add it to the distribution packages for installation. +The dotnet CLI considers any executable on the path named `dotnet-{commandName}` to be a command it can call out to. `dotnet publish`, for example, is added to the path as an executable called `dotnet-publish`. To add a new command we must create the executable and then add it to the distribution packages for installation. 0. Create an issue on https://github.com/dotnet/cli and get consensus on the need for and behavior of the command. 1. Add a new project for the command. @@ -63,4 +63,4 @@ Each command's project root should contain a manpage-style Readme.md that descri #### Add command to packages - Update the `symlinks` property of `packaging/debian/debian_config.json` to include the new command -- Update the `$Projects` property in `packaging/osx/scripts/postinstall` \ No newline at end of file +- Update the `$Projects` property in `packaging/osx/scripts/postinstall`