summaryrefslogtreecommitdiff
path: root/Documentation/workflow
diff options
context:
space:
mode:
authorstakx <stakx@eml.cc>2018-05-03 17:49:32 +0200
committerstakx <stakx@eml.cc>2018-05-03 17:49:32 +0200
commit0feb3815331c3cb0d7cda1ec99f89dd9a7b9f690 (patch)
tree98610e579b6af3361dc75f1c73afc98c90a60a1b /Documentation/workflow
parentd142ffd3ba970ca24502f49835fe8e2ea1f5558b (diff)
downloadcoreclr-0feb3815331c3cb0d7cda1ec99f89dd9a7b9f690.tar.gz
coreclr-0feb3815331c3cb0d7cda1ec99f89dd9a7b9f690.tar.bz2
coreclr-0feb3815331c3cb0d7cda1ec99f89dd9a7b9f690.zip
Some corrections in build documentation
Diffstat (limited to 'Documentation/workflow')
-rw-r--r--Documentation/workflow/UsingDotNetCli.md4
-rw-r--r--Documentation/workflow/UsingYourBuild.md2
2 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/workflow/UsingDotNetCli.md b/Documentation/workflow/UsingDotNetCli.md
index 0df0dbddf4..dd3c635977 100644
--- a/Documentation/workflow/UsingDotNetCli.md
+++ b/Documentation/workflow/UsingDotNetCli.md
@@ -121,7 +121,7 @@ C:\coreclr\helloWorld\helloWorld.csproj : warning NU1603: helloWorld depends on
### 6. Run the app
-After you publish you will find you all the binaries needed to run your application under `bin\Debug\netcoreapp2.1\win-x64\publish\`.
+After you publish you will find all the binaries needed to run your application under `bin\Debug\netcoreapp2.1\win-x64\publish\`.
To run the application simply run the EXE that is in this publish directory (it is the name of the app, or specified in the project file).
```
@@ -148,7 +148,7 @@ the further steps needed to consume the runtime nuget package.
#### 1. Update BuildNumberMinor Environment Variable
One possible problem with this technique is that Nuget assumes that distinct builds have distinct version numbers.
-Thus if you modify the source and create a new NuGet package you must it a new version number and use that in your
+Thus if you modify the source and create a new NuGet package you must give it a new version number and use that in your
application's project. Otherwise the dotnet.exe tool will assume that the existing version is fine and you
won't get the updated bits. This is what the Minor Build number is all about. By default it is 0, but you can
give it a value by setting the BuildNumberMinor environment variable.
diff --git a/Documentation/workflow/UsingYourBuild.md b/Documentation/workflow/UsingYourBuild.md
index 88afe22f9d..6a65399c16 100644
--- a/Documentation/workflow/UsingYourBuild.md
+++ b/Documentation/workflow/UsingYourBuild.md
@@ -140,7 +140,7 @@ The location is C:\coreclr\helloWorld\bin\Debug\netcoreapp2.1\win-x64\publish\Sy
## Using DotNetCli to run your .NET Core Application
-If you don't like the idea of copying files manually you can follow [this instructions](UsingDotNetCli.md) to use dotnet cli to do this for you.
+If you don't like the idea of copying files manually you can follow [these instructions](UsingDotNetCli.md) to use dotnet cli to do this for you.
However the steps described here are the simplest and most commonly used by CoreCLR developers for ad-hoc testing.
## Using CoreRun to run your .NET Core Application