Apply suggestions from code review

Co-authored-by: Daniel Beck <1831569+daniel-beck@users.noreply.github.com>
jenkinsci · Nov 9, 2020 · c0f3b7b · c0f3b7b
1 parent e28329b
commit c0f3b7b
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/faq.adoc b/docs/faq.adoc
@@ -1,4 +1,4 @@
-== FAQs
+== FAQ
 
 This document provides a quick reference for frequently questioned concepts and features in Credentials.
 

diff --git a/docs/fflags.adoc b/docs/fflags.adoc
@@ -7,7 +7,7 @@ Like any system properties, they should be considered experimental and subject t
   - Setting this property to `true` enables the _Credentials/UseOwn_ permission.
     Primarily useful when using project-based security authorization strategies or authenticated builds, this permission allows an immediate action to access user-scoped credentials from the user's private credentials store.
     Immediate actions include invoking a build with parameters, tagging a build in SCM, providing credentials to a pipeline input step, and other user interaction.
-    Using this permission can help limit which users are allowed to provide their own credentials as input to an action which can be particularly handy when combined with the Authorize Project plugin where builds may be run as the user who triggered the build.
+    Using this permission can help limit which users are allowed to provide their own credentials as input to an action which can be particularly handy when combined with the https://plugins.jenkins.io/authorize-project/[Authorize Project] plugin where builds may be run as the user who triggered the build.
     This allows separation of the permission to build a job from the permission to provide user-scoped credentials.
     When this flag is `false` or unspecified, then _Job/Build_ is used instead for the same purpose.