anchor.diff:  
   A plugin can be installed via the https://github.com/killbill/killbill-cloud/blob/master/kpm[Kill Bill Package Manager (KPM)]. For this, please follow the steps given below:
   
  -* Ensure that you have kpm installed as explained https://github.com/killbill/killbill-cloud/tree/master/kpm#kpm-installation[here]. 
  -
  -* Install the plugin as per https://docs.killbill.io/latest/plugin_development.html#_deployment_through_kpm[these] plugin installation instructions. (Use `email-notifications` as the plugin key)
  -
  -* Verify that the plugin is installed properly. This can be done by ensuring that the plugin JAR is present at the `path_to_install_plugin` specified in the previous step. Alternatively, you can also open Kpm in Kaui and verify that the email notification plugin is running as follows:
  -image:https://github.com/killbill/killbill-docs/raw/v3/userguide/assets/img/demail-notification-plugin/kaui_email_notification_plugin.png[align=center]
  +. Ensure that you have kpm installed as explained https://github.com/killbill/killbill-cloud/tree/master/kpm#kpm-installation[here]. 
  +
  +. Install the plugin using the following kpm command (Replace `<path_to_install_plugin>` with the path where you want to install the plugin. This path should match the path specified by the `org.killbill.osgi.bundle.install.dir` property in the Kill Bill configuration file):
  +[source,bash]
  +kpm install_java_plugin email-notifications --destination=<path_to_install_plugin>
  +
  +. Verify that the plugin is installed properly. This can be done by ensuring that the plugin JAR is present at the `path_to_install_plugin` specified in the previous step. Alternatively, you can also open `kpm` in https://docs.killbill.io/latest/userguide_kaui.html[Kaui] and verify that the email notification plugin is running as follows:
  +image:https://github.com/killbill/killbill-docs/raw/v3/userguide/assets/img/email-notification-plugin/kaui_email_notification_plugin.png[align=center]
  +
  +. If you would like to make changes to the plugin, you can clone the plugin code, build and deploy it as explained https://github.com/killbill/killbill-email-notifications-plugin[here]. 
   
   
   == Database Configuration
   
  -The email-notification-plugin requires some additional database tables. In order to create these tables, please follow the steps given below:
  +The email-notification-plugin requires some additional database tables. To create these tables, please follow the steps given below:
   
   * Connect to the Kill Bill database. 
   
  
positive.code:      -d '[<events>]' \
      http://127.0.0.1:8080/plugins/killbill-email-notifications/v1/accounts/{accountId}
      
  *Some notes*:
      
  . Either the tenant or the account should be configured with the events for which emails need to be sent, otherwise no emails are sent.
  
  . If a tenant is configured with some events, but account is not configured, then emails will be sent based on what is configured at the tenant level.
  
  . If a tenant is not configured with any events but account is configured with events, then emails will be sent based on what is configured at the account level. 
  
  . If both tenant and account are configured with separate events, emails will be sent based on the events configured for both.
  
  
  == Testing the plugin
  
negative.code: org.killbill.billing.plugin.email-notifications.smtp.defaultSender=xxx@yyy.com' \
  http://127.0.0.1:8080/1.0/kb/tenants/uploadPluginConfig/killbill-email-notifications
       
  . If you are on Windows, we recommend that you use https://git-scm.com/download/win[Git Bash] to run the above command. Since the above is a multiline cURL command, it may not run properly in the standard windows command prompt. Alternatively, you may also use https://www.postman.com/[Postman] to execute the tenant configuration endpoint as explained https://docs.killbill.io/latest/postman.html[here].
  
  . *Configure the account* using the following cURL command (Replace `{accountId}` with the id of the account for which emails need to be sent and `<events>` with a comma-separated list of the events for which the emails need to be sent. For example, to configure the account to send emails for *INVOICE_CREATION* and *INVOICE_PAYMENT_SUCCESS*, specify `"INVOICE_CREATION", "INVOICE_PAYMENT_SUCCESS"`):
  [source,bash]
  curl -v \
       -X POST \
  