Onboarding documentation update for CLI

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

diff --git a/docs/sections/components/component-specification/cdap-specification.rst b/docs/sections/components/component-specification/cdap-specification.rst
index 022b46d..2b26442 100755 (executable)
--- a/docs/sections/components/component-specification/cdap-specification.rst
+++ b/docs/sections/components/component-specification/cdap-specification.rst
@@ -23,8 +23,7 @@ Current Limitations and TODOs
 -----------------------------\r
 \r
 -  The integration of DMD is likely to significantly change the\r
-   :any:`Interfaces <interfaces>` section in this specification, see\r
-   :any:`DMaaP abstraction <dmaap-abstraction>`.\r
+   :any:`Interfaces <interfaces>` section in this specification.\r
 \r
 .. _parameters:\r
 \r
@@ -34,7 +33,7 @@ Parameters
 There is a ``parameters`` section in your component specification. This\r
 section contains three optional keys: `app_config <#appconfig>`__,\r
 `app_preferences <#apppreferences>`__, and\r
-`propram_preferences <#programpreferences>`__:\r
+`program_preferences <#programpreferences>`__:\r
 \r
 ::\r
 \r
@@ -146,7 +145,7 @@ Each ``program_pref`` JSON is passed into the CDAP API as the preference
 for ``program_id``.\r
 \r
 NOTE: for CDAP, this section is very likely to change when DMD is\r
-available. The *future* vision, as per :any:`DMaaP intentionally abstracted <dmaap-abstraction>` is\r
+available. The *future* vision is\r
 that you would publish your data as a series of files on HDFS, and DMD\r
 will pick them up and send them to the appropriate DMaaP feeds or\r
 directly when needed.\r