anchor.diff:  
   === System-wide configuration
   
  -Before using this plugin from a project, you must first configure some
  -system-wide settings. Go to the Jenkins system-wide configuration page
  -(*Manage Jenkins*, *Configure System*).
  -
  -The configuration for this plugin can be found in the section entitled
  -*Extended E-mail Notification*. This configuration should match the
  -settings for your SMTP mail server. This section mirrors that of the
  -https://plugins.jenkins.io/mailer/[Mailer plugin] in the *E-mail
  -Notification* section; however, there are a few additions. The fields
  -labeled *Default Subject* and *Default Content* allow you to configure
  -the subject and content on a system-wide level. The field labeled
  -*Default Recipients* can be used to set a default list of email
  -addresses for all projects using this plugin (it can be overridden at
  -the project level). This can be used to greatly simplify the
  -configuration you need to do for all projects.
  +Before using this plugin from a project, you must first configure some system-wide settings.
  +Go to the Jenkins system-wide configuration page (*Manage Jenkins*, *Configure System*).
  +
  +The configuration for this plugin can be found in the section entitled *Extended E-mail Notification*.
  +This configuration should match the settings for your SMTP mail server.
  +This section mirrors that of the https://plugins.jenkins.io/mailer/[Mailer plugin] in the *E-mail Notification* section; however, there are a few additions.
  +The fields labeled *Default Subject* and *Default Content* allow you to configure the subject and content on a system-wide level.
  +The field labeled *Default Recipients* can be used to set a default list of email addresses for all projects using this plugin (and can be overridden at the project level); this can be used to greatly simplify the configuration you need to do for all projects.
   
   === Project configuration
   
  -For a project to use this plugin, you need to enable it in the project
  -configuration page. In the *Post-build Actions* section, click on *Add
  -post-build action* and then select *Editable Email Notification*.
  -
  -There are three main fields that you can edit when this plugin is
  -enabled:
  -
  -* *Project Recipient List* - This is a comma (or whitespace)
  -separated list of email recipients. Allows you to specify a single
  -recipient list for each email that is sent.
  -* *Default Subject* - This allows you to configure a token (more
  -about tokens later) that can be used to easily configure all email
  -subjects for the project.
  -* *Default Content* - Same as *Default Subject*, but for the email
  -body instead of the subject.
  +For a project to use this plugin, you need to enable it in the project configuration page.
  +In the *Post-build Actions* section, click on *Add post-build action* and then select *Editable Email Notification*.
  +
  +There are three main fields that you can edit when this plugin is enabled:
  +
  +* *Project Recipient List* - This is a comma (or whitespace) separated list of email recipients. Allows you to specify a single recipient list for each email that is sent.
  +* *Default Subject* - This allows you to configure a token (more about tokens later) that can be used to easily configure all email subjects for the project.
  +* *Default Content* - Same as *Default Subject*, but for the email body instead of the subject.
   
   === Pipeline step
   
  -This plugin can be used from
  -https://www.jenkins.io/doc/book/pipeline/[Pipeline] via the
  -https://jenkins.io/doc/pipeline/steps/email-ext/[`emailext`] step:
  +This plugin can be used from https://www.jenkins.io/doc/book/pipeline/[Pipeline] via the https://jenkins.io/doc/pipeline/steps/email-ext/[`emailext`] step:
   
   [source,groovy]
   ----
  
positive.code: 
  === Tokens
  
  This plugin uses *tokens* to allow dynamic data to be inserted into
  recipient list, subject line, or body. A *token* is a string that starts
  with a `$` (dollar sign) and is terminated by whitespace. When an email
  is triggered, a token in the subject or content fields will be replaced
  dynamically by the actual value that it represents. Also, the value of a
  token can contain other tokens that will themselves be replaced by
  actual content. For instance, the `$DEFAULT_SUBJECT` token is replaced
  by the text (and other tokens) that is in the *Default Subject* field
  from the *Extended E-mail Notification* section of the *Configure
  System* page. Similarly, the `$PROJECT_DEFAULT_SUBJECT` token will be
  replaced by the value of the *Default Subject* field from the project
  configuration page.
  
  This plugin sets the email content fields with default values when you
  enable it for your project. The *Default Subject* and *Default Content*
  fields on the project configuration page default to `$DEFAULT_SUBJECT`
  and `$DEFAULT_CONTENT` (respectively), delegating to the the system-wide
  configuration from the *Extended E-mail Notification* section of the
  *Configure System* page. Similarly, the per-trigger content fields
  default to `$PROJECT_DEFAULT_SUBJECT` and `$PROJECT_DEFAULT_CONTENT`,
  delegating to the project's configuration. Since the value of a token
  can contain other tokens, this provides different points of
  configuration that can allow you to quickly make changes at the broadest
  level (all projects), the narrowest level (individual emails), and
  in-between (individual projects).
  
  To see a list of all available email tokens and what they display, click
  on the "?" (question mark) associated with the *Content Token Reference*
  in the *Editable Email Notification* section of the project
  configuration page.
  
  As of version 2.22, this plugin also supports tokens provided by the
  https://plugins.jenkins.io/token-macro/[Token Macro plugin]. You can see
  the available *Token Macro Plugin Tokens* below the *Extended Email
  Publisher Specific Tokens* when you click on the "?" (question mark)
  associated with the *Content Token Reference* in the *Editable Email
  Notification* section of the project configuration page.
  
  === Jelly script content templates
  
  
negative.code: 
  == Usage
  
  To see the advanced configuration for this plugin, click on the *Advanced* button.
  This section allows you to specify recipients for each type of email trigger as well as a pre-send script that can be used to modify the email prior to sending.
  
  === Pre-send Scripts and Post-send Scripts
  
  This feature allows you to write a script that can modify the https://docs.oracle.com/javaee/7/api/javax/mail/internet/MimeMessage.html[`MimeMessage`] object before or after sending the email.
  This allows adding custom headers, modifying the body, etc.
  Predefined variables include:
  
  * `msg` (https://docs.oracle.com/javaee/7/api/javax/mail/internet/MimeMessage.html[`javax.mail.internet.MimeMessage`]) - The MIME email message object, which can be modified.
  * `logger` (https://docs.oracle.com/javase/8/docs/api/java/io/PrintStream.html[`java.io.PrintStream`]) - A `PrintStream` that can be used to log messages to the build log.
  