Update README

Author: reeseschultz

README.md

@@ -42,8 +42,6 @@ torchfinder/
       deploy.yml    CI/CD pipeline
 ```
 
----
-
 ## Build
 
 The build script (`build.ts`) runs in Deno and does four things:
@@ -69,14 +67,10 @@ The `staging/` directory is what gets deployed to the `gh-pages` branch. The rep
 
 If any step fails, the script exits with a nonzero code and does not write to `staging/`. A failed build never takes down the live site.
 
----
-
 ## Local setup and contributing
 
 See [CONTRIBUTING.md](CONTRIBUTING.md) for local development setup, code conventions, and the PR process.
 
----
-
 ## Deployment
 
 Deployment is fully automated via GitHub Actions (`.github/workflows/deploy.yml`).
@@ -89,8 +83,6 @@ On a successful build, the `staging/` directory is force-pushed to the `gh-pages
 
 After a successful deploy, the workflow automatically tags the commit with the current UTC date in CalVer format. If a tag for today already exists, a numeric patch suffix is appended and incremented (`2026.02.25` → `2026.02.25.1` → `2026.02.25.2`, etc.). No manual tagging needed.
 
----
-
 ## Connection to torchfinder-data
 
 `build.ts` fetches:
@@ -105,14 +97,10 @@ This is the validated artifact produced by `torchfinder-data`'s own build step.
 
 **To report a data issue** in a specific entry: use the "Report an issue" link on the expanded entry card — it pre-fills a GitHub issue on `torchfinder-data` with the entry ID.
 
----
-
 ## Versioning
 
 Both repos use [CalVer](https://calver.org/): tags follow `YYYY.MM.DD` with an optional patch suffix (e.g., `2026.02.24.1`) for multiple releases on the same day. Tagging is automatic — the deployment workflow tags each successful deploy with the current UTC date, incrementing the patch suffix as needed.
 
----
-
 ## License
 
 All contributions to this repository are licensed under [MIT](LICENSE).