svn commit: r1767844 - /sling/site/trunk/content/documentation/development/ide-tooling/ide-tooling-incremental-build.mdtext

[kw...@apache.org]

Author: kwin
Date: Thu Nov  3 09:00:07 2016
New Revision: 1767844

URL: http://svn.apache.org/viewvc?rev=1767844&view=rev
Log:
fix some more typos

Modified:
    sling/site/trunk/content/documentation/development/ide-tooling/ide-tooling-incremental-build.mdtext

Modified: sling/site/trunk/content/documentation/development/ide-tooling/ide-tooling-incremental-build.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/ide-tooling/ide-tooling-incremental-build.mdtext?rev=1767844&r1=1767843&r2=1767844&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/ide-tooling/ide-tooling-incremental-build.mdtext (original)
+++ sling/site/trunk/content/documentation/development/ide-tooling/ide-tooling-incremental-build.mdtext Thu Nov  3 09:00:07 2016
@@ -4,7 +4,7 @@ Title: Incremental Builds in Sling IDE t
 
 ## Overview
 
-The Sling IDE Tooling relies on the [m2e incremental build support](https://wiki.eclipse.org/M2E_compatible_maven_plugins) for the generation of the bundle's manifest, the component descriptions as well as the metatype resources (the latter being generated through OSGi 6 [component annotations](https://osgi.org/javadoc/r6/cmpn/org/osgi/service/component/annotations/package-summary.html) and [metatype annotations](https://osgi.org/javadoc/r6/cmpn/org/osgi/service/metatype/annotations/package-summary.html) or through [Apache Felix SCR annotations](http://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin/scr-annotations.html). That means whenever at least one java class is touched and the auto-build in Eclipse is enabled, the annotations on that class should be reevaluated which may lead to a modification of the bundle's manifest and/or generation/modification of service description XMLs and/or Metatype resource files.
+The Sling IDE Tooling relies on the [m2e incremental build support](https://wiki.eclipse.org/M2E_compatible_maven_plugins) for the generation of the bundle's manifest, the component descriptions as well as the metatype resources (the latter two being generated through OSGi 6 [component annotations](https://osgi.org/javadoc/r6/cmpn/org/osgi/service/component/annotations/package-summary.html) and [metatype annotations](https://osgi.org/javadoc/r6/cmpn/org/osgi/service/metatype/annotations/package-summary.html) or through [Apache Felix SCR annotations](http://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin/scr-annotations.html)). That means whenever at least one java class is touched and the auto-build in Eclipse is enabled the annotations on that class should be reevaluated. This may lead to a modification of the bundle's manifest and/or generation/modification of service description XMLs and/or Metatype resource files.
 Depending on which maven plugins you use you must adjust their configuration accordingly to properly support incremental builds.
 
 ## Manifest Generation