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

[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 c6838f0  Update apicontroller.md
c6838f0 is described below

commit c6838f06196956e98d13658285122ad38410c411
Author: David Bosschaert <da...@gmail.com>
AuthorDate: Wed Aug 21 10:04:46 2019 +0100

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

diff --git a/apicontroller.md b/apicontroller.md
index 5f6b32b..a4dba94 100644
--- a/apicontroller.md
+++ b/apicontroller.md
@@ -1,8 +1,8 @@
-# API Controller and API Regions
+# API Regions
 
 If you're assembling a platform (in contrast to a final application) out of several features and provide this platform for customers to build their application on top of, additional control of the API provided by the platform is needed. The bundles within the features provide all kinds of APIs but you might not want to expose all of these as extension points. You would rather want to use some of them internally within either a single feature or share within your platform features.
 
-This is a proposal about how to add such additional metadata to the feature model. An API controller at runtime enforces the rules.
+This is a proposal about how to add such additional metadata to the feature model. An API Regions runtime component enforces the rules.
 
 # Visibility of API