[sling-org-apache-sling-capabilities] 01/01: don't use class names as example namespaces

[ju...@apache.org]

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

justin pushed a commit to branch justinedelson-patch-1
in repository https://gitbox.apache.org/repos/asf/sling-org-apache-sling-capabilities.git

commit ab5c17354c4db062452d145524176bc1627c9eef
Author: justinedelson <ju...@apache.org>
AuthorDate: Thu Jun 21 16:43:37 2018 -0400

    don't use class names as example namespaces
---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 71df24e..512f115 100644
--- a/README.md
+++ b/README.md
@@ -44,11 +44,11 @@ The `CapabilitiesServlet` produces output as in the example below, where two
     $ curl -s -u admin:admin http://localhost:8080/tmp/cap.json | jq .
     {
       "org.apache.sling.capabilities": {
-        "org.apache.sling.capabilities.internal.OsgiFrameworkCapabilitiesSource": {
+        "org.apache.sling.capabilities.osgi": {
           "framework.bundle.symbolic.name": "org.apache.felix.framework",
           "framework.bundle.version": "5.6.10"
         },
-        "org.apache.sling.capabilities.internal.JvmCapabilitiesSource": {
+        "org.apache.sling.capabilities.jvm": {
           "java.specification.version": "1.8",
           "java.vm.version": "25.171-b11",
           "java.vm.vendor": "Oracle Corporation"