chore: remove useless section for device code grant type

README.md

@@ -144,7 +144,7 @@ Where to discover learning resources about OpenID Connect.
 - [client_credentials](https://datatracker.ietf.org/doc/html/rfc6749?grant_type=client_credentials#section-4.4) - OAuth 2.0 Client Credentials Grant providing a way to get token without user interaction which fit well machine to machine communications.
 - [implicit](https://datatracker.ietf.org/doc/html/rfc6749?grant_type=implicit#section-4.2) - OAuth 2.0 Implicit Grant Type which is deprecated and should not be used anymore.
 - [password](https://datatracker.ietf.org/doc/html/rfc6749?grant_type=password#section-4.3) - OAuth 2.0 Resource Owner Password Credentials Grant Type which is not recommended to use anymore.
-- [urn:ietf:params:oauth:grant-type:device_code](https://datatracker.ietf.org/doc/html/rfc8628#section-3.4) - OAuth 2.0 Device Authorization Grant focused on interaction with user outside of a browser context like smart TVs.
+- [urn:ietf:params:oauth:grant-type:device_code](https://datatracker.ietf.org/doc/html/rfc8628) - OAuth 2.0 Device Authorization Grant focused on interaction with user outside of a browser context like smart TVs.
 - [urn:ietf:params:oauth:grant-type:jwt-bearer](https://datatracker.ietf.org/doc/html/rfc7523) - JSON Web Token (JWT) Profile for OAuth 2.0 used to authorize a client to get an access token with another JWT issued by a trusted provider.
 - [urn:ietf:params:oauth:grant-type:token-exchange](https://datatracker.ietf.org/doc/html/rfc8693) - OAuth 2.0 Token Exchange is a Grant Type which provides a way to get tokens from another token and give the ability to add an actor claim.
 - [Proof Key for Code Exchange (PKCE) Extension](https://datatracker.ietf.org/doc/html/rfc7636) - Extension of the Authorization Code flow adding security layer against code interception attack.