stop using the word 'just'

Everywhere. In documentation and code comments.

It is almost never a good word and almost always a filler that should be
avoided.

Closes #20793

docs/tests/CI.md

@@ -21,8 +21,8 @@ Every pull request is verified for each of the following:
 
 If the pull-request fails one of these tests, it shows up as a red X and you
 are expected to fix the problem. If you do not understand what the issue is or
-have other problems to fix the complaint, just ask and other project members
-can likely help out.
+have other problems to fix the complaint, ask and other project members can
+likely help out.
 
 Consider the following table while looking at pull request failures:
 
@@ -46,7 +46,7 @@ Windows jobs have a number of flaky issues, most often, these:
 - test run crashing with fork errors.
 - steps past the test run exiting with -1073741502 (hex C0000142).
 
-In these cases you can just try to update your pull requests to rerun the tests
+In these cases you can try to update your pull requests to rerun the tests
 later as described below.
 
 A detailed overview of test runs and results can be found on

docs/tests/FILEFORMAT.md

@@ -165,7 +165,7 @@ Available substitute variables include:
 - `%FTP6PORT` - IPv6 port number of the FTP server
 - `%FTPPORT` - Port number of the FTP server
 - `%FTPSPORT` - Port number of the FTPS server
-- `%FTPTIME2` - Timeout in seconds that should be just sufficient to receive a
+- `%FTPTIME2` - Timeout in seconds that should be sufficient to receive a
   response from the test FTP server
 - `%GOPHER6PORT` - IPv6 port number of the Gopher server
 - `%GOPHERPORT` - Port number of the Gopher server
@@ -401,7 +401,7 @@ issue.
 - `auth_required` if this is set and a POST/PUT is made without auth, the
   server does NOT wait for the full request body to get sent
 - `delay: [msecs]` - delay this amount after connection
-- `idle` - do nothing after receiving the request, just "sit idle"
+- `idle` - do nothing after receiving the request, "sit idle"
 - `stream` - continuously send data to the client, never-ending
 - `writedelay: [msecs]` delay this amount between reply packets
 - `skip: [num]` - instructs the server to ignore reading this many bytes from
@@ -587,8 +587,7 @@ Set the given environment variables to the specified value before the actual
 command is run. They are restored back to their former values again after the
 command has been run.
 
-If the variable name has no assignment, no `=`, then that variable is just
-deleted.
+If the variable name has no assignment, no `=`, then that variable is deleted.
 
 ### `<command [option="no-q/no-output/no-include/no-memdebug/force-output/binary-trace"] [timeout="secs"][delay="secs"][type="perl/shell"]>`
 Command line to run.

docs/tests/HTTP.md

@@ -27,8 +27,8 @@ tests/http/test_01_basic.py .....
 
 Pytest takes arguments. `-v` increases its verbosity and can be used several
 times. `-k <expr>` can be used to run only matching test cases. The `expr` can
-be something resembling a python test or just a string that needs to match
-test cases in their names.
+be something resembling a python test or a string that needs to match test
+cases in their names.
 
 ```sh
 curl/tests/http> pytest -vv -k test_01_02
@@ -138,8 +138,8 @@ left behind.
 
 Tests making use of these fixtures have them in their parameter list. This
 tells pytest that a particular test needs them, so it has to create them.
-Since one can invoke pytest for just a single test, it is important that a
-test references the ones it needs.
+Since one can invoke pytest for a single test, it is important that a test
+references the ones it needs.
 
 All test cases start with `test_` in their name. We use a double number scheme
 to group them. This makes it ease to run only specific tests and also give a

docs/tests/TEST-SUITE.md

@@ -194,8 +194,8 @@ ensure that the memory log file is properly written even if curl crashes.
 
 If a test case fails, you can conveniently get the script to invoke the
 debugger (gdb) for you with the server running and the same command line
-parameters that failed. Just invoke `runtests.pl <test number> -g` and then
-just type 'run' in the debugger to perform the command through the debugger.
+parameters that failed. Simply invoke `runtests.pl <test number> -g` and then
+type 'run' in the debugger to perform the command through the debugger.
 
 ### Logs
 
@@ -286,9 +286,9 @@ Each test has a master file that controls all the test data. What to read,
 what the protocol exchange should look like, what exit code to expect and
 what command line arguments to use etc.
 
-These files are `tests/data/test[num]` where `[num]` is just a unique
-identifier described above, and the XML-like file format of them is
-described in the separate [`FILEFORMAT`](FILEFORMAT.md) document.
+These files are `tests/data/test[num]` where `[num]` is a unique identifier
+described above, and the XML-like file format of them is described in the
+separate [`FILEFORMAT`](FILEFORMAT.md) document.
 
 ### curl tests