Clarify feedstock-webservices relation

Author: zklaus

docs/maintainer/infrastructure.md

@@ -498,6 +498,7 @@ Authenticated services involved:
 
 The conversion of new recipes in `staged-recipes` to their respective feedstocks
 happens in a cron job run by `admin-requests`. For more details see [admin-requests](#admin-requests).
+As part of the feedstock creation, the new feedstock receives a webhook connecting it with the [webservices](#admin-web-services).
 
 ### Feedstock changes
 
@@ -508,7 +509,7 @@ Pushes to `main` or other branches:
 - The automated initialization commits following approval in `staged-recipes`.
   These are generated by `conda-smithy` and pushed by the automation in `admin-requests`.
 - Automated maintenance commits triggered from `admin-migrations`.
-- Rerender requests are handled by instances of `conda-forge/webservices-dispatch-action` and triggered by the admin web service.
+- Rerender requests are handled by instances of `conda-forge/webservices-dispatch-action` and triggered by the [webservices](#admin-web-services).
 
 Automatic pull requests can be opened by...