Replace instances of scie-pants-linux-x86_64 with pants (#74)

Fixes #73 with a
find-and-replace of "scie-pants-linux-x86_64" with "pants".

Verified only reference directories have been modified (`git diff --stat
| grep /docs/`)

docs/reference/global-options.mdx

@@ -317,9 +317,9 @@ ignore_warnings = [
 
 Use this Pants version. Note that Pants only uses this to verify that you are using the requested version, as Pants cannot dynamically change the version it is using once the program is already running.
 
-If you use the `scie-pants-linux-x86_64` script from https://www.pantsbuild.org/v2.20/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.
+If you use the `pants` script from https://www.pantsbuild.org/v2.20/docs/installation, however, changing the value in your `pants.toml` will cause the new version to be installed and run automatically.
 
-Run `scie-pants-linux-x86_64 --version` to check what is being used.
+Run `pants --version` to check what is being used.
 
 </Option>
 
@@ -832,7 +832,7 @@ Whether or not to use nailgun to run JVM requests that are marked as supporting
   default_repr={`3`}
 >
 
-The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `scie-pants-linux-x86_64 run`) before killing it.
+The time in seconds to wait when gracefully shutting down an interactive process (such as one opened using `pants run`) before killing it.
 
 </Option>
 

docs/reference/goals/experimental-bsp.mdx

@@ -79,7 +79,7 @@ Run the Build Server Protocol server. Pants will receive BSP RPC requests via th
 
 Environment variables to set in the BSP runner script when setting up BSP in a repository. Entries are either strings in the form `ENV_VAR=value` to set an explicit value; or just `ENV_VAR` to copy the value from Pants' own environment when the experimental-bsp goal was run.
 
-This option only takes effect when the BSP runner script is written. If the option changes, you must run `scie-pants-linux-x86_64 experimental-bsp` again to write a new copy of the BSP runner script.
+This option only takes effect when the BSP runner script is written. If the option changes, you must run `pants experimental-bsp` again to write a new copy of the BSP runner script.
 
 Note: The environment variables passed to the Pants BSP server will be those set for your IDE and not your shell. For example, on macOS, the IDE is generally launched by `launchd` after clicking on a Dock icon, and not from the shell. Thus, any environment variables set for your shell will likely not be seen by the Pants BSP server. At the very least, on macOS consider writing an explicit PATH into the BSP runner script via this option.
 

docs/reference/goals/fix.mdx

@@ -47,7 +47,7 @@ You can repeat this option, e.g. `fix --only=autoflake --only=pyupgrade` or `fix
 
 If true, skip running all formatters.
 
-FYI: when running `scie-pants-linux-x86_64 fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible.
+FYI: when running `pants fix fmt ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `fix` where possible.
 
 </Option>
 

docs/reference/goals/generate-lockfiles.mdx

@@ -33,7 +33,7 @@ Only generate lockfiles for the specified resolve(s).
 
 Resolves are the logical names for the different lockfiles used in your project. For your own code's dependencies, these come from backend-specific configuration such as `[python].resolves`. For tool lockfiles, resolve names are the options scope for that tool such as `black`, `pytest`, and `mypy-protobuf`.
 
-For example, you can run `scie-pants-linux-x86_64 generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`.
+For example, you can run `pants generate-lockfiles --resolve=black --resolve=pytest --resolve=data-science` to only generate lockfiles for those two tools and your resolve named `data-science`.
 
 If you specify an invalid resolve name, like 'fake', Pants will output all possible values.
 
@@ -75,7 +75,7 @@ Include unchanged distributions in the diff summary output. Implies `diff=true`.
   default_repr={`None`}
 >
 
-If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `scie-pants-linux-x86_64 generate-lockfiles --resolve=<name>` like normal.
+If set, lockfile headers will say to run this command to regenerate the lockfile, rather than running `pants generate-lockfiles --resolve=<name>` like normal.
 
 </Option>
 

docs/reference/goals/lint.mdx

@@ -47,7 +47,7 @@ You can repeat this option, e.g. `lint --only=flake8 --only=shellcheck` or `lint
 
 If true, skip running all formatters in check-only mode.
 
-FYI: when running `scie-pants-linux-x86_64 fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible.
+FYI: when running `pants fmt lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fmt` when running `lint` where possible.
 
 </Option>
 
@@ -61,7 +61,7 @@ FYI: when running `scie-pants-linux-x86_64 fmt lint ::`, there should be diminis
 
 If true, skip running all fixers in check-only mode.
 
-FYI: when running `scie-pants-linux-x86_64 fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible.
+FYI: when running `pants fix lint ::`, there should be diminishing performance benefit to using this flag. Pants attempts to reuse the results from `fix` when running `lint` where possible.
 
 </Option>