You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by da...@apache.org on 2019/04/10 15:48:10 UTC

[sling-org-apache-sling-feature] branch master updated: Update readme.md

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

davidb pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-org-apache-sling-feature.git


The following commit(s) were added to refs/heads/master by this push:
     new 3537ea3  Update readme.md
     new adf5ccc  Merge pull request #11 from bendiesel/patch-1
3537ea3 is described below

commit 3537ea367002983bd94bba0efacaae11c5c26cc5
Author: bendiesel <be...@gmail.com>
AuthorDate: Wed Apr 10 07:59:57 2019 -0700

    Update readme.md
    
    Fixed typo
---
 readme.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/readme.md b/readme.md
index 2a91f8e..749a2b8 100644
--- a/readme.md
+++ b/readme.md
@@ -10,7 +10,7 @@ server-side systems and cloud and container based architectures.
 As these applications are generally based on many bundles, describing each bundle individually in the application 
 definition becomes unwieldy once the number of bundles reaches a certain level. 
 
-Addinally, OSGi has no mechanism to describe other elements of the application definition, such as configuration or custom artifacts.
+Additionally, OSGi has no mechanism to describe other elements of the application definition, such as configuration or custom artifacts.
 
 The Sling OSGi Feature Model introduces a higher level to describe OSGi applications that encapsulates the details of the various 
 components that the application is built up from. It allows the description of an entire OSGi-based application based on reusable