[sling-org-apache-sling-feature] branch master updated: Small editorial change

[da...@apache.org]

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 00b9ef3  Small editorial change
00b9ef3 is described below

commit 00b9ef3837cc3d0dd296d22b6effdf6c8981990e
Author: David Bosschaert <bo...@adobe.com>
AuthorDate: Wed Jun 6 15:47:04 2018 +0100

    Small editorial change
---
 apicontroller.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/apicontroller.md b/apicontroller.md
index 1168f83..eab064a 100644
--- a/apicontroller.md
+++ b/apicontroller.md
@@ -15,7 +15,7 @@ We can generalize this by saying that API is either globally visible (to every c
 
 Without any further information, API is globally visible by default. However, for platform features we want the opposite as we want to ensure that newly added API is not world-wide visible by default. Therefore we'll add an additional build time check (analyzer) that checks that each platform feature has an api controller configuration as below.
 
-A feature can have an additional extension JSON named regions. This example exposes some packages to the global region and an additional package to the platform region. Exports declared earlier in the api-regions array also apply to later elements in the array, so the platform region also contains all exports declared for the global region.
+A feature can have an additional extension JSON named api-regions. This example exposes some packages to the global region and an additional package to the platform region. Exports declared earlier in the api-regions array also apply to later elements in the array, so the platform region also contains all exports declared for the global region.
 
     "api-regions:JSON|false" : [
         {
@@ -47,7 +47,7 @@ A feature can also just consume packages from a region, without having to export
 
 If the api-regions extension is missing or the api-regions information is missing, it is assumed that all packages are exported to the "global" region and all packages in the global region are visible to the feature.
 
-If a feature exports no packages and only wants to import packages from the global region, this can be specified as follows:
+If a feature exports no packages and only wants to have visibility of packages from the global region, this can be specified as follows:
     
     "api-regions:JSON|false" : [ "global" ]
 

-- 
To stop receiving notification emails like this one, please contact
davidb@apache.org.