From 71fc04c4acca9f07490d770acb332da9ac8c4b0c Mon Sep 17 00:00:00 2001 From: Daniel Houston Date: Wed, 24 Jan 2018 17:29:03 -0700 Subject: [PATCH] Updated security definitions text link to reference the Security Definitions Object in the 2.0 spec --- versions/2.0.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/versions/2.0.md b/versions/2.0.md index 5916e30c3e..6efb8531f9 100755 --- a/versions/2.0.md +++ b/versions/2.0.md @@ -2239,13 +2239,13 @@ read:pets: read your pets Lists the required security schemes to execute this operation. The object can have multiple security schemes declared in it which are all required (that is, there is a logical AND between the schemes). -The name used for each property MUST correspond to a security scheme declared in the [Security Definitions](#securityDefinitionsObject). +The name used for each property MUST correspond to a security scheme declared in the [Security Definitions Object](#securityDefinitionsObject). ##### Patterned Fields Field Pattern | Type | Description ---|:---:|--- -{name} | [`string`] | Each name must correspond to a security scheme which is declared in the [Security Definitions](#securityDefinitions). If the security scheme is of type `"oauth2"`, then the value is a list of scope names required for the execution. For other security scheme types, the array MUST be empty. +{name} | [`string`] | Each name must correspond to a security scheme which is declared in the [Security Definitions Object](#securityDefinitionsObject). If the security scheme is of type `"oauth2"`, then the value is a list of scope names required for the execution. For other security scheme types, the array MUST be empty. ##### Security Requirement Object Examples