[DOCS] Changes wording to move away from data frame terminology in St…

…ack Docs. (elastic#534)
szabosteve · Sep 25, 2019 · 59f6582 · 59f6582
1 parent 36b7406
commit 59f6582
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 3 deletions.
diff --git a/docs/en/stack/ml/df-analytics/dfanalytics-limitations.asciidoc b/docs/en/stack/ml/df-analytics/dfanalytics-limitations.asciidoc
@@ -19,10 +19,11 @@ the Elastic {dfanalytics} feature:
 
 [float]
 [[dfa-deletion-limitations]]
-=== Deleting a {dfanalytics-job} does not delete the {dataframe} destination index
+=== Deleting a {dfanalytics-job} does not delete the destination index
 
 The {ref}/delete-dfanalytics.html[delete {dfanalytics-job} API] does not delete
-the {dataframe} destination index. That index must be deleted separately.
+the destination index that contains the annotated data of the {dfanalytics}. 
+That index must be deleted separately.
 
 [float]
 [[dfa-update-limitations]]

diff --git a/docs/en/stack/ml/df-analytics/evaluatedf-api.asciidoc b/docs/en/stack/ml/df-analytics/evaluatedf-api.asciidoc
@@ -17,7 +17,7 @@ results of an {oldetection} analysis by using {binarysc}.
 
 To evaluate the {dfanalytics} with this API, you need to annotate your index 
 that contains the results of the analysis with a field that marks each 
-{dataframe} row with the ground truth. For example, in case of {oldetection}, 
+document with the ground truth. For example, in case of {oldetection}, 
 the field must indicate whether the given data point really is an outlier or 
 not. The {evaluatedf-api} evaluates the performance of the {dfanalytics} against 
 this manually provided ground truth.