@@ -23,7 +23,7 @@ and what is required to implement and register one.
23
23
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
24
24
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
25
25
specification are to be interpreted as described in
26
- [[ RFC2119] ( https://tools.ietf.org/html/rfc2119 ) ] .
26
+ [[ RFC2119] [ rfc-2119 ] ] .
27
27
28
28
### 1.2. Abbreviations
29
29
@@ -35,7 +35,7 @@ Manager for Windows" is abbreviated to "GCM for Windows" or "GCM Windows".
35
35
"Git Credential Manager for Mac & Linux" is abbreviated to "GCM for
36
36
Mac/Linux" or "GCM Mac/Linux".
37
37
38
- OAuth2 [[ RFC6749] ( https://tools.ietf.org/html/rfc6749 ) ] "access tokens" are
38
+ OAuth2 [[ RFC6749] [ rfc-6749 ] ] "access tokens" are
39
39
abbreviated to "ATs" and "refresh tokens" to "RTs". "Personal Access Tokens" are
40
40
abbreviated to "PATs".
41
41
@@ -334,7 +334,7 @@ If a host provider wishes to surface custom commands the SHOULD implement the
334
334
335
335
Each provider is given the opportunity to create a single ` ProviderCommand `
336
336
instance 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 ] ] .
338
338
339
339
There are no limitations on what format sub-commands, arguments, or options must
340
340
take, 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.
346
346
[ gcm ] : https://github.com/GitCredentialManager/git-credential-manager
347
347
[ github-dotnet-cli ] : https://github.com/dotnet/command-line-api
348
348
[ 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