badwords: avoid 'simply'

It's mostly a filler word. I've read through each use of it in the code
base and did minor rephrasings when "simply" carried some meaning. The
overwhelming majority of cases, removing it improved the text
significantly. Inspired by #20793.

Closes #20822
This commit is contained in:
Felipe Mesquita 2026-03-05 10:40:16 -03:00 committed by Viktor Szakats
parent 4021c6e673
commit f25124338c
No known key found for this signature in database
71 changed files with 108 additions and 108 deletions

View file

@ -136,14 +136,14 @@ Force the test to run even if mentioned in DISABLED.
Run the given test(s) with gdb. This is best used on a single test case and
curl built --disable-shared. This then fires up gdb with command line set to
run the specified test case. Simply (set a break-point and) type 'run' to
run the specified test case. Set a break-point if needed and type 'run' to
start.
## `-gl`
Run the given test(s) with lldb. This is best used on a single test case and
curl built --disable-shared. This then fires up lldb with command line set to
run the specified test case. Simply (set a break-point and) type 'run' to
run the specified test case. Set a break-point if needed and type 'run' to
start.
## `-gw`
@ -313,7 +313,7 @@ use.
The test script checks most of these by itself to determine when it is safe to
attempt to run each test. Those which cannot be run due to failed requirements
are simply skipped and listed at the completion of all test cases. In some
are skipped and listed at the completion of all test cases. In some
unusual configurations, the test script cannot make the correct determination
for all tests. In these cases, the problematic tests can be skipped using the
"!keyword" skip feature documented earlier.