This is an automated email from the ASF dual-hosted git repository.

pottlinger pushed a commit to branch vote-0.4-incubating-01
in repository https://gitbox.apache.org/repos/asf/incubator-tamaya-site.git

commit 8e59f81aba994c72781e91f255fd79d91b3da078
Author: Hugo Hirsch <git...@hugo-hirsch.de>
AuthorDate: Tue Aug 27 23:09:02 2019 +0200

    Fix Tamaya as Standards, harmonize OSGi
---
 .../documentation/extensions/mod_usagetracker.adoc  |  2 +-
 content/tamayaasastandard.adoc                      | 21 ++++++++++-----------
 2 files changed, 11 insertions(+), 12 deletions(-)

diff --git a/content/documentation/extensions/mod_usagetracker.adoc 
b/content/documentation/extensions/mod_usagetracker.adoc
index 395c048..00b6a65 100644
--- a/content/documentation/extensions/mod_usagetracker.adoc
+++ b/content/documentation/extensions/mod_usagetracker.adoc
@@ -148,7 +148,7 @@ DATE: Sat Apr 30 21:51:09 CEST 2016
 A special feature of this module is that it observes +ConfigEvent+ published 
through Tamaya'as event channel
 (+tamaya-events+ module). If no metaconfiguration model is found the model 
manager by default automatically creates
 models for all injected instances on the fly. In the case of CDI integration 
this happens typically during deployment
-time, since CDI initializes during deployment time. Other runtime platforms, 
such as OSGI, may have rather different
+time, since CDI initializes during deployment time. Other runtime platforms, 
such as OSGi, may have rather different
 behaviour. Nevertheless this means that after your system has been started you 
should have access to a complete
 set of +ConfigModel+ instances that automatically document all the classes in 
your system that consume configuration
 (through injection).
diff --git a/content/tamayaasastandard.adoc b/content/tamayaasastandard.adoc
index 8d6a3a8..e026707 100644
--- a/content/tamayaasastandard.adoc
+++ b/content/tamayaasastandard.adoc
@@ -11,10 +11,10 @@ provide a long term stable configuration solution.
 
 Tamaya implements a recent state of the Configuration JSR. The exact commit
 version of the JSR API implemented (the JSR has not yet released any version
-as of now) can be evaluated looing at the _tamaya-jsr382_ `pom.xml` in the
+as of now) can be evaluated by looking at the _tamaya-jsr382_ `pom.xml` in the
 sandbox repository.
 
-To use Tamaya aS a JSR-382 Configuration provider you must add the following
+To use Tamaya as a JSR-382 Configuration provider you must add the following
 dependency:
 
 [source,xml]
@@ -27,8 +27,7 @@ dependency:
 ---------
 
 Since this component is not yet officially released you must use the current 
snapshot
-version +0.4-incubating-SNAPSHOT+. You also must add the Apache Snapshot
-Repository to your build:
+version +0.4-incubating-SNAPSHOT+. In order for that to work, you need to add 
the Apache Snapshot Repository to your build:
 
 [source,xml]
 ---------
@@ -46,7 +45,7 @@ Repository to your build:
 ---------
 
 
-== Microprofile
+== Microprofile Configuration API
 
 Tamaya implements the Microprofile Configuration API Version 1.1. To use Tamaya
 as a Micropropfile Configuration provider you must add the following 
dependency:
@@ -61,14 +60,14 @@ as a Micropropfile Configuration provider you must add the 
following dependency:
 ---------
 
 
-== OSGI ConfigAdmin
+== OSGi ConfigAdmin
 
-Tamaya's OSGI Support leverages the OSGI 
+org.osgi.service.cm.ConfigurationAdmin+
-configuration manager as defined in OSGI Compendiumn Version +4.3.1+. Hereby
-Tamaya can add or modify Configuration in OSGI, which may trigger change 
events.
+Tamaya's OSGi Support leverages the OSGi 
+org.osgi.service.cm.ConfigurationAdmin+
+configuration manager as defined in OSGi Compendium Version +4.3.1+. Hereby
+Tamaya can add or modify Configuration in OSGi, which may trigger change 
events.
 The exact behaviour can be controlled in many ways. By default Tamaya, does 
not change
-anything, when deployed in OSGI, without being configured todo so. For details
-check link:documentation/extensions/mod_osgi.html[Tamaya's OSGI Documentation].
+anything, when deployed in OSGi, without being configured todo so. For details
+check link:documentation/extensions/mod_osgi.html[Tamaya's OSGi Documentation].
 
 
 

Reply via email to