languages/dart-sdk
languages/dart-sdk
1
0
Fork 0
mirror of https://github.com/dart-lang/sdk synced 2024-09-06 00:59:09 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix a typo and a link in docs

Browse source 
Change-Id: Ic65318796672dc0eb5f1efb84dcb371042031937
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/368561
Reviewed-by: Devon Carew <devoncarew@google.com>
Reviewed-by: Kevin Moore <kevmoo@google.com>
Commit-Queue: Ömer Ağacan <omersa@google.com>
This commit is contained in:
Ömer Sinan Ağacan 2024-05-30 07:13:09 +00:00 committed by Commit Queue
parent bd4ae9b309
commit 416f532385
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/Status-files.md
View file

@ -70,7 +70,7 @@ dart2js, should produce a CompileError".
[clue]: https://en.wikipedia.org/wiki/Cluedo
With miles of tests and piles of configurtions, we need a compact notation for
With miles of tests and piles of configurations, we need a compact notation for
defining expectations. That's what status files aim to be.
A status file is a line-oriented (newlines are significant) plain text file.

2
docs/Testing.md
View file

@ -152,7 +152,7 @@ behavior was the last time we ran the test under some configuration. We call
this the test's **status**.
In the past, status was recorded in a separate set of
[**status files**][Status-files.md]. These live in the repo under `tests/`.
[**status files**](Status-files.md). These live in the repo under `tests/`.
In order to change the expected
behavior of a test, you had to manually change the status file and then commit
that change. In practice, we found this doesn't scale to the number of tools and