Merge "Fix minor typos and broken links on doc homepage"

[docs.git] / docs / getting-started-guide / concepts_and_tools.rst

diff --git a/docs/getting-started-guide/concepts_and_tools.rst b/docs/getting-started-guide/concepts_and_tools.rst
index 20e9450a00a6403b320a773394da940e5ebe4908..fa702a5e42e96c82322e5597969ddf46d62d3556 100644 (file)
--- a/docs/getting-started-guide/concepts_and_tools.rst
+++ b/docs/getting-started-guide/concepts_and_tools.rst
@@ -20,17 +20,10 @@ below.
 * **Apache Karaf** provides a lightweight runtime to install the Karaf features
   you want to implement and is included in the OpenDaylight platform software.
   By default, OpenDaylight has no pre-installed features.
-* After installing OpenDaylight, you install your selected features using the
-  Karaf console to expand networking capabilities. In the Karaf feature list
-  below are the ones you’re most likely to use when creating your network
-  environment.
 
-  As a short example of installing a Karaf feature, OpenDaylight
-  offers Application Layer Traffic Optimization (ALTO). The Karaf feature to
-  install ALTO is odl-alto-release. On the Karaf console, the command to
-  install it is:
-
-  feature:install odl-alto-release
+  Features and feature repositories can be managed in the Karaf configuration
+  file  ``etc/org.apache.karaf.features.cfg`` using the ``featuresRepositories``
+  and ``featuresBoot`` variables.
 
 * Model-Driven Service Abstraction Layer (MD-SAL) is the OpenDaylight framework
   that allows developers to create new Karaf features in the form of services
@@ -39,15 +32,14 @@ below.
 
   a. A shared datastore that maintains the following tree-based structures:
 
-    i. The Config Datastore, which maintains a representation of the desired
-       network state.
-    #. The Operational Datastore, which is a representation of the actual
-       network state based on data from the managed network elements.
+     i. The Config Datastore, which maintains a representation of the desired
+        network state.
+     #. The Operational Datastore, which is a representation of the actual
+        network state based on data from the managed network elements.
 
   b. A message bus that provides a way for the various services and protocol
      drivers to notify and communicate with one another.
 
-* If you’re interacting with OpenDaylight through DLUX or the REST APIs while
+* If you’re interacting with OpenDaylight through the REST APIs while
   using the the OpenDaylight interfaces, the microservices architecture allows
   you to select available services, protocols, and REST APIs.
-