Many dozens (hundreds?) of documentation code blocks were indented to
match the surrounding XML or just arbitrarily. The thing is: Inside
<programlisting> tags, similar to <pre> tags, line feeds and leading
whitespace are being preserved, which looked very awkward in the HTML
documentation. While a few files were mostly correct in this respect,
which shows that it was meant to be like that, many others were not.
This was tedious, stupid work to fix, but it had to be done.

Please note that the documentation was in no way updated content-wise.
This is also overdue, but not my focus here.

Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>

Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>

	  	issingleton or issingleton()?

  Finally documented matching difference between exacttype and patterntype

  49784  declaring interface methods should work as it does in interfaces
  70794  The introduction on interface causes the interface implementation class error

  underspecification of primitive conversion

  Specify how does args pointcut collect context for pointcuts which are used in cflow

  static aspects not well explained

  Define MethodPattern, FieldPattern, ConstructorPattern terms

  "Specify context collecting behavior for this, target and args pointcuts"

in semantics guide more meaningful

	  	The introduction on interface causes the interface implementation class error
(Feel free to edit my text if you feel more eloquent...)

 	proceed used as method name in around advice

 	if-pointcuts with side-effects

 	Stale ITD example code in Programming Guide

 	Cannot assign to final fields in intertype constructors.

When creating obj thru intro constructor init code fails to execute

effect of an after returning type incompatible with a join point return type

  * added note about String+ and Foo.class to implementation notes section

 * changed "Implementation Limitations" to "Implementation Notes" inside ProgGuide
 * added section on bytecode limitations, headed by handler issues.

  * changed "aspect aspect" to "abstract aspect"

  * manually applied excellent doc patch contributed by Nick Brett

 * fix to semantics document to describe correct semantics
 * checkin of failing coverage test case for correct semantics

  Bugzilla Bug 35551: "declare soft" in abstract aspect have no effect
Specifying that declare soft behaves like advice in that
it must be concretized to have an effect.