Skip to content

Commit 161171e

Browse files
committed
Apply suggestions
1 parent 21b85a3 commit 161171e

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -147,8 +147,8 @@ variable with a fallback version or requirement. In this case it is important to
147147
also use the bazel flag `--repo_env=LLVM_VERSION=version_or_requirement`. It is
148148
important to use both correctly because otherwise the resulting builds are not
149149
reproducible. The main purpose of using an environment variable to encode the
150-
version is for integration or batch testing on multiple platforms where multiple
151-
LLVM version should be tested.
150+
version for integration or batch testing on multiple platforms where multiple
151+
LLVM versions should be tested.
152152

153153
- `getenv(ENVIRONMENT_VARIABLE_NAME,fallback)`
154154

@@ -167,7 +167,7 @@ llvm.toolchain(
167167
In this example, MacOS x86 machines have their LLVM version hard-coded to
168168
`15.0.7`. For all other targets the LLVM version is read from the environment
169169
variable `LLVM_VERSION` which must be referenced on the Bazel command line as
170-
explained above. If the variabel is not present, then the LLVM version defaults
170+
explained above. If the variable is not present, then the LLVM version defaults
171171
to the requirement expression `latest:>=17.0.0,<20`.
172172

173173
### Selecting Toolchains

0 commit comments

Comments
 (0)