summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorAdeel Mujahid <adeelbm@outlook.com>2017-06-28 15:02:16 (GMT)
committerDan Moseley <danmose@microsoft.com>2017-06-28 15:02:16 (GMT)
commit217ab30d021f27be6fe4f35126a88e592366acbf (patch)
tree9fafc35ab1c1e44427626bd0d956be39e1d87cb9 /README.md
parent68673ed19e7c5e849258ef4be90ec9577226ee64 (diff)
downloadcoreclr-217ab30d021f27be6fe4f35126a88e592366acbf.zip
coreclr-217ab30d021f27be6fe4f35126a88e592366acbf.tar.gz
coreclr-217ab30d021f27be6fe4f35126a88e592366acbf.tar.bz2
Cleanup some instances of project.json from the repo (#12484)
* Replace ScriptGenerator project.json with csproj * Update project.json occurrences in docs Fix few typos. * Remove project.json comments
Diffstat (limited to 'README.md')
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 378ce52..abd081a 100644
--- a/README.md
+++ b/README.md
@@ -90,7 +90,7 @@ you use `dotnet.exe` for this).
These extra pieces are not defined here, however you don't need to build them in order to use the CoreCLR
Nuget package you create here. There are already versions of the CoreFX packages published on
-https://www.nuget.org/ so you can have your test application's project.json specify the CoreCLR you
+https://www.nuget.org/ so you can have your test application's project file specify the CoreCLR you
built and it will naturally pull anything else it needs from the official location https://www.nuget.org/ to
make a complete application. More on this in the [Using Your Build](Documentation/workflow/UsingYourBuild.md) page.