docs: correct accuracy gaps in installation and contributing guides

- installing.rst: fix the conda command (`conda install -c conda-forge
  dataretrieval`, not `conda -c conda-forge install ...`).
- contributing.rst: the package version is derived from Git tags by
  setuptools_scm, so the "edit the version in setup.py / conf.py" steps
  are obsolete — replace them with the tag-based release note. Bump the
  supported Python from "3.6, 3.7, 3.8" to "3.9 and later" (matches
  pyproject `requires-python` and the CI matrix: 3.9/3.13/3.14).
- CONTRIBUTING.md: update stale `USGS-python/dataretrieval` issue URLs to
  `DOI-USGS/dataretrieval-python`, `blob/master` -> `blob/main`, the
  Python version list to "3.9 and later", and fix an "interace" typo.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: thodson-usgs

CONTRIBUTING.md

@@ -36,7 +36,7 @@ however writing code is not the only way to contribute.
 
 ### Reporting Bugs
 
-Report bugs at https://github.com/USGS-python/dataretrieval/issues.
+Report bugs at https://github.com/DOI-USGS/dataretrieval-python/issues.
 
 When reporting a bug, please include:
 
@@ -49,7 +49,7 @@ When reporting a bug, please include:
 
 ### Fixing Bugs
 
-Look through the GitHub [issues](https://github.com/USGS-python/dataretrieval/issues)
+Look through the GitHub [issues](https://github.com/DOI-USGS/dataretrieval-python/issues)
 for known and unresolved bugs. Any issues labeled "bug" that are unassigned,
 are open for resolution. You are welcome to comment in the relevant issue to
 state your intention to resolve the bug, which will help ensure there is no
@@ -68,7 +68,7 @@ your fork, to the original upstream repository.
 
 ### Implementing Features
 
-Look through the GitHub [issues](https://github.com/USGS-python/dataretrieval/issues)
+Look through the GitHub [issues](https://github.com/DOI-USGS/dataretrieval-python/issues)
 for outstanding feature requests. Anything tagged with "enhancement"
 and "please-help" is open to whomever wants to implement it.
 
@@ -83,8 +83,8 @@ Before you submit a pull request, check that it meets these guidelines:
 2. If the pull request adds or modifies functionality, the documentation should
    be updated. To do so, either add or modify a functions docstring which will
    automatically become part of the API documentation
-3. The pull request should work for Python 3.7, 3.8, 3.9, 3.10 - refer to the
-   [python-package.yml file](https://github.com/USGS-python/dataretrieval/blob/master/.github/workflows/python-package.yml)
+3. The pull request should work for Python 3.9 and later - refer to the
+   [python-package.yml file](https://github.com/DOI-USGS/dataretrieval-python/blob/main/.github/workflows/python-package.yml)
    for the latest versions of Python being tested by the continuous integration
    pipelines. This will be checked automatically by the CI pipelines once the
    pull request is opened.
@@ -98,7 +98,7 @@ via any automated processes or pipelines.
 #### Style
 
 * Attempt to write code following the [PEP8 style guidelines](https://peps.python.org/pep-0008/) as much as possible
-* The public interace should emphasize functions over classes; however, classes
+* The public interface should emphasize functions over classes; however, classes
   can and should be used internally and in tests
 * Functions for downloading data from a specific web portal must be grouped
   within their own submodule
@@ -202,7 +202,7 @@ will need to do the following (in a separate branch of the repository):
 ### Submitting Feedback
 
 The best way to send feedback is to open an issue at
-https://github.com/USGS-python/dataretrieval/issues.
+https://github.com/DOI-USGS/dataretrieval-python/issues.
 
 Please be as clear as possible in your feedback, if you are reporting a bug
 refer to [Reporting Bugs](#reporting-bugs).
@@ -211,7 +211,7 @@ refer to [Reporting Bugs](#reporting-bugs).
 ### Feature Requests
 
 To request or propose a new feature, open an issue at
-https://github.com/USGS-python/dataretrieval/issues.
+https://github.com/DOI-USGS/dataretrieval-python/issues.
 
 Please be sure to:
 * Explain in detail how it would work, possibly with pseudo-code or an example

docs/source/meta/contributing.rst

@@ -64,24 +64,25 @@ Before you submit a pull request, check that it meets these guidelines:
 2. If the pull request adds functionality, the docs should be updated. Put
    your new functionality into a function with a docstring, and add the
    feature to the list in README.md.
-3. The pull request should work for Python 3.6, 3.7, 3.8, and pass the GitHub
+3. The pull request should work for Python 3.9 and later, and pass the GitHub
    Actions continuous integration pipelines.
 
 
 Updating Package Version:
-^^^^^^^^^^^^^^^^^^^^^^^^^
+^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 Follow semantic versioning as best as possible. This means that changing the
 first digit of the version indicates a breaking change. Any smaller changes
 should attempt to maintain backwards-compatibility with previous code and
 issue deprecation warnings for features or functionality that will be removed
 or no longer be backwards-compatible in future releases.
 
-When updating the package version, there are currently two places where this
-must be done:
-
-1. In the `setup.py` file the version field should be updated
-2. In the `conf.py` file both the version and release fields can be updated
+The package version is derived automatically from Git tags by
+``setuptools_scm`` (see ``[tool.setuptools_scm]`` in ``pyproject.toml``), so
+there is no version string to edit by hand. To cut a release, tag the commit
+(for example, ``git tag v1.2.3``) and push the tag; both the installed package
+version and the documentation's ``version`` and ``release`` values (read via
+``importlib.metadata`` in ``docs/source/conf.py``) follow from it.
 
 
 Coding Standards

docs/source/meta/installing.rst

@@ -30,7 +30,7 @@ To install the latest stable release of ``dataretrieval`` from the
 
 .. code-block:: bash
 
-    $ conda -c conda-forge install dataretrieval
+    $ conda install -c conda-forge dataretrieval
 
 .. _conda-forge channel: https://anaconda.org/conda-forge/dataretrieval