You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by ss...@apache.org on 2016/11/21 15:15:30 UTC

svn commit: r1770697 - /sling/site/trunk/content/documentation/bundles/models.mdtext

Author: sseifert
Date: Mon Nov 21 15:15:30 2016
New Revision: 1770697

URL: http://svn.apache.org/viewvc?rev=1770697&view=rev
Log:
fix typo, unify writing for "since" clauses

Modified:
    sling/site/trunk/content/documentation/bundles/models.mdtext

Modified: sling/site/trunk/content/documentation/bundles/models.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/models.mdtext?rev=1770697&r1=1770696&r2=1770697&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/bundles/models.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/models.mdtext Mon Nov 21 15:15:30 2016
@@ -49,7 +49,7 @@ Constructor injection is also supported
         }
     }
 
-Because the name of a contructor argument parameter cannot be detected via the Java Reflection API a `@Named` annotation is mandatory for injectors that require a name for resolving the injection.
+Because the name of a constructor argument parameter cannot be detected via the Java Reflection API a `@Named` annotation is mandatory for injectors that require a name for resolving the injection.
 
 In order for these classes to be picked up, there is a header which must be added to the bundle's manifest:
 
@@ -413,7 +413,7 @@ To create a custom annotation, implement
 This interface may be implemented by the same class as implements an injector, but this is not strictly necessary. Please refer to the
 injectors in [Subversion](http://svn.apache.org/repos/asf/sling/trunk/bundles/extensions/models/impl/src/main/java/org/apache/sling/models/impl/injectors/) for examples.
  
-# Specifying an Alternate Adapter Class (Since Sling Models 1.1.0)
+# Specifying an Alternate Adapter Class (since 1.1.0)
 
 By default, each model class is registered using its own implementation class as adapter. If the class has additional interfaces this is not relevant.
 
@@ -439,7 +439,7 @@ SPI interface which could use context to
 content path context. If multiple implementations of the `ImplementationPicker` interface are present, they are queried
 one after another in order of their service ranking property, the first one that picks an implementation wins.
 
-# Associating a Model Class with a Resource Type (Since Sling Models 1.3.0)
+# Associating a Model Class with a Resource Type (since 1.3.0)
 
 The `@Model` annotation provides an optional `resourceType` attribute which allows for model classes to be associated with one or
 more resource types. This is used in three different ways.
@@ -451,7 +451,7 @@ The `ModelFactory` service interface has
 
 The resource type is also used as part of the Exporter framework (see next section).
 
-# Exporter Framework (Since Sling Models 1.3.0)
+# Exporter Framework (since 1.3.0)
 
 Sling Models objects can be exported to arbitrary Java objects through the Sling Models Exporter framework. Model objects can be
 programatically exported by calling the `ModelFactory` method `exportModel()`. This method takes as its arguments: