diff options
author | Tom <tom.zille@gmail.com> | 2017-10-10 18:21:14 +0200 |
---|---|---|
committer | Stephen Toub <stoub@microsoft.com> | 2017-10-10 12:21:14 -0400 |
commit | ea23b794eaa7f5bf595da55e2ff5ea6025a1c772 (patch) | |
tree | 7d5df8b60107f634e3a1f57f9d66bfb9828712ec /README.md | |
parent | be3715cbba1022c95bb668d45521016b0414bc25 (diff) | |
download | coreclr-ea23b794eaa7f5bf595da55e2ff5ea6025a1c772.tar.gz coreclr-ea23b794eaa7f5bf595da55e2ff5ea6025a1c772.tar.bz2 coreclr-ea23b794eaa7f5bf595da55e2ff5ea6025a1c772.zip |
Fixing a Typo in README.md (#14405)
Just deleted one of the two "for"s in the Setting up your GIT Clone of the CoreCLR Repository.
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -102,7 +102,7 @@ make a complete application. More on this in the [Using Your Build](Documentati The first step in making a build of the CoreCLR Repository is to clone it locally. If you already know how to do this, just skip this section. Otherwise if you are developing on windows you can see [Setting Up A Git Repository In Visual Studio 2017](https://github.com/Microsoft/perfview/blob/master/documentation/SettingUpRepoInVS.md) -for for instructions on setting up. This link uses a different repository as an example, but the issues (do you fork or not) and +for instructions on setting up. This link uses a different repository as an example, but the issues (do you fork or not) and the procedure are equally applicable to this repository. -------------------------- |