chore: use DIST_ANME in docs

- easier to read than NORMALIZED_DIST_NAME
- addresses part of #986

Author: RonnyPfannschmidt

docs/config.md

@@ -157,7 +157,7 @@ Callables or other Python objects have to be passed in `setup.py` (via the `use_
         it is strongly recommended to use distribution-specific pretend versions
         (see below).
 
-`SETUPTOOLS_SCM_PRETEND_VERSION_FOR_${NORMALIZED_DIST_NAME}`
+`SETUPTOOLS_SCM_PRETEND_VERSION_FOR_${DIST_NAME}`
 :   used as the primary source for the version number,
     in which case it will be an unparsed string.
     Specifying distribution-specific pretend versions will

docs/integrations.md

@@ -47,7 +47,7 @@ build:
       - export SETUPTOOLS_SCM_OVERRIDES_FOR_${READTHEDOCS_PROJECT//-/_}='{scm.git.pre_parse="fail_on_shallow"}'
 ```
 
-This configuration uses the `SETUPTOOLS_SCM_OVERRIDES_FOR_${NORMALIZED_DIST_NAME}` environment variable to override the `scm.git.pre_parse` setting specifically for your project when building on ReadTheDocs, forcing setuptools-scm to fail with a clear error if the repository is shallow.
+This configuration uses the `SETUPTOOLS_SCM_OVERRIDES_FOR_${DIST_NAME}` environment variable to override the `scm.git.pre_parse` setting specifically for your project when building on ReadTheDocs, forcing setuptools-scm to fail with a clear error if the repository is shallow.
 
 ## CI/CD and Package Publishing
 
@@ -67,7 +67,7 @@ These local version components (`+g1a2b3c4d5`, `+dirty`) prevent uploading to Py
 
 #### The Solution
 
-Use the `SETUPTOOLS_SCM_OVERRIDES_FOR_${NORMALIZED_DIST_NAME}` environment variable to override the `local_scheme` to `no-local-version` when building for upload to PyPI.
+Use the `SETUPTOOLS_SCM_OVERRIDES_FOR_${DIST_NAME}` environment variable to override the `local_scheme` to `no-local-version` when building for upload to PyPI.
 
 ### GitHub Actions Example
 
@@ -287,9 +287,9 @@ publish-release:
 
 #### Environment Variable Format
 
-The environment variable `SETUPTOOLS_SCM_OVERRIDES_FOR_${NORMALIZED_DIST_NAME}` must be set where:
+The environment variable `SETUPTOOLS_SCM_OVERRIDES_FOR_${DIST_NAME}` must be set where:
 
-1. **`${NORMALIZED_DIST_NAME}`** is your package name normalized according to PEP 503:
+1. **`${DIST_NAME}`** is your package name normalized according to PEP 503:
    - Convert to uppercase
    - Replace hyphens and dots with underscores
    - Examples: `my-package` → `MY_PACKAGE`, `my.package` → `MY_PACKAGE`

docs/overrides.md

@@ -7,7 +7,7 @@ setuptools-scm provides a mechanism to override the version number build time.
 the environment variable `SETUPTOOLS_SCM_PRETEND_VERSION` is used
 as the override source for the version number unparsed string.
 
-to be specific about the package this applies for, one can use `SETUPTOOLS_SCM_PRETEND_VERSION_FOR_${NORMALIZED_DIST_NAME}`
+to be specific about the package this applies for, one can use `SETUPTOOLS_SCM_PRETEND_VERSION_FOR_${DIST_NAME}`
 where the dist name normalization follows adapted PEP 503 semantics.
 
 ## pretend metadata
@@ -17,7 +17,7 @@ setuptools-scm provides a mechanism to override individual version metadata fiel
 The environment variable `SETUPTOOLS_SCM_PRETEND_METADATA` accepts a TOML inline table
 with field overrides for the ScmVersion object.
 
-To be specific about the package this applies for, one can use `SETUPTOOLS_SCM_PRETEND_METADATA_FOR_${NORMALIZED_DIST_NAME}`
+To be specific about the package this applies for, one can use `SETUPTOOLS_SCM_PRETEND_METADATA_FOR_${DIST_NAME}`
 where the dist name normalization follows adapted PEP 503 semantics.
 
 ### Supported fields
@@ -82,7 +82,7 @@ export SETUPTOOLS_SCM_PRETEND_METADATA='{node="g1337beef", distance=4}'
 
 ## config overrides
 
-setuptools-scm parses the environment variable `SETUPTOOLS_SCM_OVERRIDES_FOR_${NORMALIZED_DIST_NAME}`
+setuptools-scm parses the environment variable `SETUPTOOLS_SCM_OVERRIDES_FOR_${DIST_NAME}`
 as a toml inline map to override the configuration data from `pyproject.toml`.
 
 ## subprocess timeouts

docs/usage.md

@@ -221,7 +221,7 @@ Note that running this Dockerfile requires docker with BuildKit enabled
 
 To avoid BuildKit and mounting of the .git folder altogether, one can also pass the desired
 version as a build argument.
-Note that `SETUPTOOLS_SCM_PRETEND_VERSION_FOR_${NORMALIZED_DIST_NAME}`
+Note that `SETUPTOOLS_SCM_PRETEND_VERSION_FOR_${DIST_NAME}`
 is preferred over `SETUPTOOLS_SCM_PRETEND_VERSION`.