Tweaks to casing / linking

Author: rvedotrc

versions/3.1.1.md

@@ -326,11 +326,11 @@ The `security` field describes how requests are authorized:
 
 - If omitted, then nothing can be inferred about the authorization requirements; the behaviour is implementation-defined.
 - If present but empty (`security: []`), then the behaviour is undefined.
-- Otherwise, it is an array of security requirement objects, only one of which needs to be satisfied for the request to be authorized.
+- Otherwise, it is an array of Security Requirement Objects, only one of which needs to be satisfied for the request to be authorized.
 
-Because the empty [security requirement object](#security-requirement-object) `{}` will always be satisfied, any `security` list of Security Requirement Objects that includes `{}` will allow all requests. In particular, `security: [{}]` means that no security schemes are in use (also known as "no security").
+Because the empty [Security Requirement Object](#security-requirement-object) `{}` will always be satisfied, any `security` list that includes `{}` will allow all requests. In particular, `security: [{}]` means that no security schemes are in use (also known as "no security").
 
-Individual operations [can override this field](#operation-security).
+Individual Operations can [override this field](#operation-security).
 
 #### Info Object