anchor.diff:  
   Also, don't forget to check our http://killbill.io/blog/[blog], which has interesting articles about some of Kill Bill internals, use cases, ...
   
  -*Most of our documentation is hosted in a https://github.com/killbill/killbill-docs[github repository], so please either submit a PR when obvious things are missing or wrong, or let us know so we can improve it!*
  +*Most of our documentation is hosted in a https://github.com/killbill/killbill-docs[GitHub repository], so please either submit a PR when obvious things are missing or wrong, or let us know so we can improve it!*
   
   === Where To Start?
   
  +This obviously depends on the type of audience, and also whether you are looking for a Billing System, or a Payment System.
   
  -This obviously depends on the type of audience, and also whether you are looking for a Billing System, or a Payment System.
   If your goal is to get a sense of what Kill Bill provides, and assuming you are at least slightly technical, here is a good start:
   
   1. Read through the user guides (all 3)
  
positive.code: * http://killbill.io/userguide/platform-userguide[user guides],
  * http://killbill.io/tutorials/[tutorials],
  * https://www.youtube.com/channel/UChXICgGipKvJbtzKfM1SNoQ[screencasts],
  * In addition to that, we also provide documentation for each specific plugin in the github plugin repository using the `Readme.rd` file. An example of such documentation can be seen for the https://github.com/killbill/killbill-avatax-plugin[Avatax plugin].
  
  
  The user guides are split into 3 different pages:
  
negative.code: // Bug for aligning the caption https://github.com/asciidoctor/asciidoctor/issues/857 [caption="Kill Bill Logical Architecture",align=center]
  image::https://docs.google.com/drawings/d/1OCYn6GTrmEbJi9daT8L9xPCgwp7n5FidTWH0nHpCYqE/pub?w=960&amp;h=480[align=center]
  
  Contrary to most billing solutions, Kill Bill is *not* a batch oriented system, but instead, it is driven by events occurring in the system (for example, the creation of a new subscription will create a new event that the invoicing core service will process and as result a new invoice may be created along with a new event, which the payment code service will then process, ...)
  
  Kill Bill is traditionally packaged as a war and is therefore executed within a web container (for example Tomcat). It offers REST APIs <TODO LINK> to manage all the state associated to accounts, subscriptions, invoices, payments, ... It also provides lower level (java) APIs and can therefore be embedded as a library within a (java) user application.
  
  === Documentation
  
  Our documentation is targeted for different types of audience:
  
  * Kill Bill Visitors: technical or non-technical folks interested to know more about what Kill Bill is about.
  * Kill Bill Users: technical folks that are interested to evaluate the solution or are ready to deploy it.
  * Kill Bill Developers: technical folks that are interested to contribute to the open-source project (often to enhance the platform to suit their own specific needs).
  
  For the *Kill Bill Visitors*, we provide an overview of the product on our http://killbill.io[main web site], and also http://killbill.io/features[some more details about the features].
  
  