Show the complete setup sequence in Quick Start and usage docs

The examples previously jumped from creating a StaticFiles instance
to wrapping the app with middleware, skipping the mount call that
connects them. Both README and usage docs now show all three pieces:
create, mount, wrap.

The usage docs also explain that file hashes are computed once at
startup, so readers know to restart the ASGI process after deploying
new static files.

Author: audreyfeldroy

README.md

@@ -28,8 +28,11 @@ from staticware import StaticFiles, StaticRewriteMiddleware
 # Point at your static files directory
 static = StaticFiles("static")
 
+# Mount it however your framework mounts sub-apps:
+app.mount("/static", static)
+
 # Wrap any ASGI app to rewrite static paths in HTML responses
-app = StaticRewriteMiddleware(your_app, static=static)
+app = StaticRewriteMiddleware(app, static=static)
 
 # In templates, resolve cache-busted URLs:
 static.url("styles.css")       # /static/styles.a1b2c3d4.css

docs/usage.md

@@ -8,11 +8,18 @@ Create a `StaticFiles` instance pointing at your static files directory, then wr
 from staticware import StaticFiles, StaticRewriteMiddleware
 
 static = StaticFiles("static")
-app = StaticRewriteMiddleware(your_app, static=static)
+
+# Mount it however your framework mounts sub-apps:
+app.mount("/static", static)
+
+# Wrap the app to rewrite static paths in HTML responses:
+app = StaticRewriteMiddleware(app, static=static)
 ```
 
 `StaticFiles` hashes every file in the directory at startup. When a browser requests the hashed filename, it gets an immutable cache header. When it requests the original filename, the file is served without aggressive caching.
 
+File hashes are computed once when `StaticFiles` is created. If you deploy updated static files, restart the ASGI process to pick up the new hashes. This is the same model used by Starlette and most ASGI static file handlers.
+
 ## Resolving URLs in Templates
 
 Use `static.url()` to get the cache-busted URL for a file: