From aa878161e91001724c339595f224cbcdb5cd3cd5 Mon Sep 17 00:00:00 2001 From: cbracketdash Date: Wed, 13 Jan 2021 19:08:58 -0800 Subject: [PATCH] readme: fix some minor typos (#8098) --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 1358e79d43..92d5437da3 100644 --- a/README.md +++ b/README.md @@ -76,7 +76,7 @@ That's it! Now you have a V executable at `[path to V repo]/v`. Now you can try `./v run examples/hello_world.v` (`v.exe` on Windows). -V is being constantly updated. To update V, simply run: +V is constantly being updated. To update V, simply run: ```bash v up @@ -84,7 +84,7 @@ v up ### C compiler -It's recommended to use Clang or GCC or Visual Studio. +It's recommended to use Clang, GCC, or Visual Studio. If you are doing development, you most likely already have one of those installed. Otherwise, follow these instructions: @@ -94,7 +94,7 @@ Otherwise, follow these instructions: - [Installing a C compiler on Windows](https://github.com/vlang/v/wiki/Installing-a-C-compiler-on-Windows) However, if none is found when running `make` on Linux or Windows, -TCC would be downloaded and set as an alternative C backend. +TCC is downloaded as the default C backend. It's very lightweight (several MB) so this shouldn't take too long. ### Symlinking @@ -119,7 +119,7 @@ shell, cd to the path, where you have compiled v.exe, then type: .\v.exe symlink ``` -That will make v available everywhere, by adding it to your PATH. +That will make V available everywhere, by adding it to your PATH. Please restart your shell/editor after that, so that it can pick the new PATH variable.