diff --git a/README.md b/README.md
index 95e39ae..a4ebf2a 100644
--- a/README.md
+++ b/README.md
@@ -1,12 +1,51 @@
 # GitHub Pull Request Comment Build Plugin
 
 This plugin listens for comments on pull requests and will trigger a GitHub multibranch
-job if a comment body matches the configured value, such as "REBUILD". This is implemented
-as a branch property on multibranch jobs.
+job if a comment body matches the configured value, such as "rerun the build".
+This is implemented as a branch property on multibranch jobs.
+
+To enable this behavior, simply add one or more of the branch properties from
+this plugin to the multibranch job and configure the regular expression to use.
+
+![GitHub Multibranch Job Configuration](docs/branch-property-strategy.png)
+
+Please ensure that you have a GitHub server properly connected via the Jenkins configuration,
+or else the plugin will not operate correctly.
+
+## Regular expression matching
+
+The regex is not surrounded with any markers and uses the
+`Pattern.CASE_INSENSITIVE` and `Pattern.DOTALL` Java flags.
+
+For example, `^rerun the build$` only matches comments that contain no other
+text besides "rerun the build" (case insensitive), while `rebuild` would match
+comments such as
+
+```
+Please
+rebuild this
+```
+
+and
+
+```
+Commence the rebuilding
+```
+
+If no pattern is provided, `^REBUILD$` is used.
+
+## GitHub organization folders
+
+When using the GitHub organization folders approach to creating multibranch
+pipeline jobs, the branch properties may not be edited [according to
+design](https://issues.jenkins-ci.org/browse/JENKINS-33900?focusedCommentId=326187&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-326187).
+Instead, use the functionality built into the GitHub Plugin with using the
+[issueCommentTrigger](https://github.com/jenkinsci/pipeline-github-plugin#issuecommenttrigger)
+in your pipeline script. This works in a similar way to this plugin. The main
+advantage of this plugin is that it may be used from the Job DSL plugin to
+create jobs with this branch property already added (in the case when you don't
+trust pipeline scripts, etc).
 
-To enable this behavior, simply add the branch property to the multibranch job and 
-configure the string to use. Make sure that you have a GitHub server properly connected 
-via the Jenkins configuration, or else this will not work.
 
 # Plugin maintenance
 
diff --git a/docs/branch-property-strategy.png b/docs/branch-property-strategy.png
new file mode 100644
index 0000000..8d043d4
Binary files /dev/null and b/docs/branch-property-strategy.png differ