Merge "Onboarding documentation update for CLI"

[dcaegen2.git] / docs / sections / components / component-type-cdap.rst

diff --git a/docs/sections/components/component-type-cdap.rst b/docs/sections/components/component-type-cdap.rst
index 0f5150f..f2dce6c 100755 (executable)
--- a/docs/sections/components/component-type-cdap.rst
+++ b/docs/sections/components/component-type-cdap.rst
@@ -65,10 +65,7 @@ Future DMaaP abstraction
 Shown below is our *vision* for how DMaaP is abstracted from component\r
 developers:\r
 \r
-.. figure:: ../images/dmdvision.png\r
-   :alt: Screenshot\r
-\r
-   Screenshot\r
+.. figure:: ./images/dmdvision.png\r
 \r
 Today, this is a vision; it is not in place. Today, each CDAP app is\r
 built with built in assumptions about where they are getting their data\r
@@ -84,7 +81,7 @@ of by the platform. They should be spending their time on the problem at
 hand—the analytic.\r
 \r
 This also allows each CDAP application to have a standard set of\r
-interfaces: HTTP and HDFS: |Screenshot|\r
+interfaces: HTTP and HDFS: \r
 \r
-.. |Screenshot| image:: ../images/io.png\r
+.. figure::  ./images/io.png\r
 \r