diff --git a/src/main/resources/Documentation/config.md b/src/main/resources/Documentation/config.md
index 5365d8e..3eff578 100644
--- a/src/main/resources/Documentation/config.md
+++ b/src/main/resources/Documentation/config.md
@@ -81,10 +81,6 @@
     html = "<a href=\"http://jira.example.com/browse/$1\">$1</a>"
     association = SUGGESTED
 
-Once a Git commit with a comment link is detected, the Jira issue ID
-is extracted and a new comment is added to the issue, pointing back to
-the original Git commit.
-
 Jira connectivity
 -----------------
 
@@ -138,62 +134,3 @@
            optional
     Issue-id enforced in commit message [MANDATORY/?]: suggested
 
-GitWeb integration
-----------------
-
-When Gerrit gitweb is configured, an additional direct link from Jira to GitWeb
-will be created, pointing exactly to the Git commit ID containing the Jira issue ID.
-
-Issues workflow automation
---------------------------
-
-Jira plugin is able to automate status transition on the issues based on
-code-review actions performed on Gerrit; actions are performed on Jira using
-the username/password provided during Gerrit init.
-Transition automation is driven by `$GERRIT_SITE/etc/issue-state-transition.config`
-file.
-
-Syntax of the status transition configuration file is the following:
-
-    [action "<issue-status-action>"]
-    change=<state-change-type>
-    verified=<verified-value>
-    code-review=<code-review-value>
-
-`<issue-status-action>`
-:	Action to be performed on the Jira issue when all the condition in the stanza are met.
-
-`<state-change-type>`
-:	Gerrit state change type on which the action will be triggered.
-	Possible values are: `created`, `commented`, `merged`, `abandoned`,
-	`restored`
-
-`<verified-value>`
-:	Verified label added on the Gerrit change with a value from -1 to +1
-
-`<code-review-value>`
-:	Code-Review label added on the Gerrit change with a value from -2 to +2
-
-Note: multiple conditions in the action stanza are possible but at least one must be present.
-
-Example:
-
-    [action "Start Progress"]
-    change=created
-
-    [action "Resolve Issue"]
-    verified=+1
-    code-review=+2
-
-    [action "Close Issue"]
-    change=merged
-
-    [action "Stop Progress"]
-    change=abandoned
-
-The above example defines four status transitions on Jira, based on the following conditions:
-
-* Whenever a new Change is created on Gerrit, start progress on the Jira issue
-* Whenever a change is verified and reviewed with +2, set the Jira issue to resolved
-* Whenever a change is merged to the branch, close the Jira issue
-* Whenever a change is abandoned, stop the progress on the Jira issue