X-Git-Url: https://gerrit.linuxfoundation.org/infra/gitweb?a=blobdiff_plain;f=docs%2Fjjb%2Flf-release-jobs.rst;h=a2cfd95582dbe1f3057014eab3dd26425dab0094;hb=refs%2Fchanges%2F06%2F16706%2F2;hp=f07c4e556ceb273f90dd1c0ca1c54b83ba0f3c06;hpb=d528f52b9ebd3c9982045e4cb754eb8bd0f1e007;p=releng%2Fglobal-jjb.git

diff --git a/docs/jjb/lf-release-jobs.rst b/docs/jjb/lf-release-jobs.rst
index f07c4e55..a2cfd955 100644
--- a/docs/jjb/lf-release-jobs.rst
+++ b/docs/jjb/lf-release-jobs.rst
@@ -9,14 +9,14 @@ Jenkins will pick this up and sign the ref extrapolated by log_dir and promote t
 
 Maven release jobs can also trigger via "Build with parameters" negating the need for a release file.
 The parameters will need to be filled out in the same was as a release file's would, excepting the speacial
-RELEASE_FILE parameter which will need to be set to False to inform the job that it should not expect a release file.
+USE_RELEASE_FILE parameter which will need to be set to False to inform the job that it should not expect a release file.
 The Special Parameters are as follows:
 
 GERRIT_BRANCH = master
 VERSION = 1.0.0
 LOG_DIR = example-project-maven-stage-master/17/
 DISTRIBUTION_TYPE = maven
-RELEASE_FILE = False
+USE_RELEASE_FILE = false
 
 .. note::