Correct stale sponsor use case and user-flow docs

Author: JacobCoffee

apps/sponsors/use_cases.py

@@ -134,10 +134,11 @@ def execute(self, contract, **kwargs):
 
 
 class ExecuteExistingContractUseCase(BaseUseCaseWithNotifications):
-    """Execute a contract with an already-signed document file.
+    """Execute a contract using a document the sponsor signed outside the app.
 
-    Lets PSF staff upload contracts that weren't generated by the sponsors app.
-    Expected to become legacy once all contracts are created through the app.
+    Backs the admin "approve signed sponsorship" action: the contract is created on
+    approval and executed immediately, bypassing the usual status checks. Any other
+    active sponsorship of the same sponsor is marked as overlapped by this one.
     """
 
     notifications = [

docs/source/administration.rst

@@ -106,10 +106,12 @@ they represent:
 :contract.py: The `Contract` model which is used to generate the final contract document and other
               support models;
 
-The sponsors app is mostly an administrative one. The only part regular users interact with is
-the sponsorship application form, available at ``/sponsors/application/new/``. Every other
-operation should be done via the admin action buttons on the ``Sponsorship`` and ``Contract``
-models.
+Regular users interact with the sponsors app in two places: the application flow
+(benefit selection at ``/sponsors/application/``, then the form at
+``/sponsors/application/new/``) and the sponsorship dashboard at ``/users/sponsorships/``,
+where sponsors view their sponsorships, update sponsor information, and upload required
+assets. Everything else is done through the admin action buttons on the ``Sponsorship``
+and ``Contract`` models.
 
 Agreements
 ----------