fixup! docs: document client authentication

Author: dhensby

docs/api/handlers/token-handler.md

@@ -44,7 +44,7 @@ Token Handler.
 Get the client from the model.
 
 Client authentication is delegated to the configured authentication
-methods (see [module:client-authentication](module:client-authentication)). The single method
+methods (see the client authentication guide). The single method
 that matches the request resolves and verifies the client; supported out
 of the box are HTTP Basic, request-body credentials and public clients,
 plus any methods added via `extendedClientAuthentication` (e.g. JWT

docs/guide/client-authentication.md

@@ -177,7 +177,7 @@ Content-Type: application/x-www-form-urlencoded
 grant_type=client_credentials
 &scope=read
 &client_assertion_type=urn%3Aietf%3Aparams%3Aoauth%3Aclient-assertion-type%3Ajwt-bearer
-&client_assertion=eyJhbGciOiJSUzI1Niİ...
+&client_assertion=eyJhbGciOiJSUzI1Ni...
 ```
 
 A client can build the assertion with [`jose`](https://github.com/panva/jose):
@@ -199,7 +199,7 @@ const clientAssertion = await new SignJWT({})
 
 ## Writing a custom method
 
-Implement the [`AbstractClientAuthentication`](../api/server.md) port and register it through
+Implement the [`AbstractClientAuthentication`](../api/client-authentication/abstract-client-authentication) port and register it through
 `extendedClientAuthentication`. For example, a minimal `tls_client_auth` (mTLS) adapter:
 
 ```js
@@ -214,7 +214,7 @@ class TlsClientAuthentication extends AbstractClientAuthentication {
   matches (request) { return !!request.get('x-ssl-client-cert') }
 
   // The `token_endpoint_auth_method` this request presents (for pinning).
-  presentedMethod () { return 'tls_client_auth' }
+  presentedMethod (request) { return 'tls_client_auth' }
 
   // Verify the credentials and resolve the client (throw InvalidClientError on failure).
   async authenticate (request, { model }) {