@@ -23,7 +23,7 @@ and what is required to implement and register one.
2323The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
2424"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
2525specification are to be interpreted as described in
26- [[ RFC2119] ( https://tools.ietf.org/html/rfc2119 ) ] .
26+ [[ RFC2119] [ rfc-2119 ] ] .
2727
2828### 1.2. Abbreviations
2929
@@ -35,7 +35,7 @@ Manager for Windows" is abbreviated to "GCM for Windows" or "GCM Windows".
3535"Git Credential Manager for Mac & Linux" is abbreviated to "GCM for
3636Mac/Linux" or "GCM Mac/Linux".
3737
38- OAuth2 [[ RFC6749] ( https://tools.ietf.org/html/rfc6749 ) ] "access tokens" are
38+ OAuth2 [[ RFC6749] [ rfc-6749 ] ] "access tokens" are
3939abbreviated to "ATs" and "refresh tokens" to "RTs". "Personal Access Tokens" are
4040abbreviated to "PATs".
4141
@@ -334,7 +334,7 @@ If a host provider wishes to surface custom commands the SHOULD implement the
334334
335335Each provider is given the opportunity to create a single ` ProviderCommand `
336336instance to which further sub-commands can be parented to. Commanding is
337- provided by the ` System.CommandLine ` API library [[ 1] ( # references) ] .
337+ provided by the ` System.CommandLine ` API library [[ 1] [ references ] ] .
338338
339339There are no limitations on what format sub-commands, arguments, or options must
340340take, but implementors SHOULD attempt to follow existing practices and styles.
@@ -346,3 +346,6 @@ take, but implementors SHOULD attempt to follow existing practices and styles.
346346[ gcm ] : https://github.com/GitCredentialManager/git-credential-manager
347347[ github-dotnet-cli ] : https://github.com/dotnet/command-line-api
348348[ hostprovider-base-class ] : #26-hostprovider-base-class
349+ [ references ] : #references
350+ [ rfc-2119 ] : https://tools.ietf.org/html/rfc2119
351+ [ rfc-6749 ] : https://tools.ietf.org/html/rfc6749
0 commit comments