Fix inaccurate example list in podTemplateSpec section

spec.resources is a first-class field on MCPRemoteProxy, so listing
resource limits among options 'not exposed as first-class fields' is
misleading. Swap for affinity rules, which genuinely require
podTemplateSpec.

Author: github-actions[bot]

docs/toolhive/guides-k8s/remote-mcp-proxy.mdx

@@ -458,8 +458,8 @@ via `AssumeRoleWithWebIdentity` and signs requests with SigV4. See the
 ### Customize the remote proxy pod
 
 Use `podTemplateSpec` to set pod-level options that aren't exposed as
-first-class fields on `MCPRemoteProxy`, such as security contexts, resource
-limits, node selectors, and tolerations. The field follows the standard
+first-class fields on `MCPRemoteProxy`, such as security contexts, node
+selectors, tolerations, and affinity rules. The field follows the standard
 Kubernetes
 [`PodTemplateSpec`](https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-template-v1/#PodTemplateSpec)
 format, and you only need to specify the fields you want to add or override.