correction for drop graph, collection handling

3.10/graphs-satellite-graphs-management.md

@@ -197,27 +197,31 @@ sharding for other collections (`edges`).
  {% endarangoshexample %}
  {% include arangoshexample.html id=examplevar script=script result=result %}
 
-You may drop the complete graph, but remember to drop collections that you
-might have removed from the graph beforehand, as they will not be part of the
-graph definition anymore and thus not be dropped for you. Alternatively, you
-can `truncate` the graph if you just want to get rid of the data.
+You may drop the complete graph including the underlying collections by setting
+the second argument in the call to `_drop()` to `true`. This will only drop
+collections that are in the graph definition at that point. Remember to manually
+drop collections that you might have removed from the graph beforehand.
 
  {% arangoshexample examplevar="examplevar" script="script" result="result" %}
  @startDocuBlockInline satelliteGraphManagementModify5_cluster
  @EXAMPLE_ARANGOSH_OUTPUT{satelliteGraphManagementModify5_cluster}
  var graph_module = require("@arangodb/satellite-graph");
  var relation = graph_module._relation("edges", "vertices", "vertices");
  var graph = graph_module._create("myGraph", [relation], []);
- graph._deleteEdgeDefinition("edges");
- graph._removeVertexCollection("vertices");
- graph_module._drop("myGraph", true); // does not drop any collections
+ graph._deleteEdgeDefinition("edges"); // Remove edge collection from graph definition
+ graph._removeVertexCollection("vertices"); // Remove vertex collection from graph definition
+ graph_module._drop("myGraph", true); // Does not drop any collections because none are left in the graph definition
+ // Manually clean up the collections that were left behind
  db._drop("edges"); // drop before sharding-defining 'vertices' collection
  db._drop("vertices");
  @END_EXAMPLE_ARANGOSH_OUTPUT
  @endDocuBlock satelliteGraphManagementModify5_cluster
  {% endarangoshexample %}
  {% include arangoshexample.html id=examplevar script=script result=result %}
 
+Alternatively, you can `truncate()` all collections of the graph if you just
+want to get rid of the data but keep the collections and graph definition.
+
 ### Remove an edge collection
 
 Delete an edge definition from the graph:

3.10/graphs-smart-graphs-management.md

@@ -230,27 +230,31 @@ sharding for other collections (`edges`).
 {% endarangoshexample %}
 {% include arangoshexample.html id=examplevar script=script result=result %}
 
-You may drop the complete graph, but remember to drop collections that you
-might have removed from the graph beforehand, as they will not be part of the
-graph definition anymore and thus not be dropped automatically. Alternatively, you
-can `truncate` all collections from the graph if you just want to get rid of the data.
+You may drop the complete graph including the underlying collections by setting
+the second argument in the call to `_drop()` to `true`. This will only drop
+collections that are in the graph definition at that point. Remember to manually
+drop collections that you might have removed from the graph beforehand.
 
 {% arangoshexample examplevar="examplevar" script="script" result="result" %}
  @startDocuBlockInline smartGraphModify5_cluster
  @EXAMPLE_ARANGOSH_OUTPUT{smartGraphModify5_cluster}
  var graph_module = require("@arangodb/smart-graph");
  var relation = graph_module._relation("edges", "vertices", "vertices");
  var graph = graph_module._create("myGraph", [relation], [], {smartGraphAttribute: "region", numberOfShards: 9});
- graph._deleteEdgeDefinition("edges");
- graph._removeVertexCollection("vertices");
- graph_module._drop("myGraph", true); // does not drop any collections
+ graph._deleteEdgeDefinition("edges"); // Remove edge collection from graph definition
+ graph._removeVertexCollection("vertices"); // Remove vertex collection from graph definition
+ graph_module._drop("myGraph", true); // Does not drop any collections because none are left in the graph definition
+ // Manually clean up the collections that were left behind
  db._drop("edges"); // drop before sharding-defining 'vertices' collection
  db._drop("vertices");
  @END_EXAMPLE_ARANGOSH_OUTPUT
  @endDocuBlock smartGraphModify5_cluster
 {% endarangoshexample %}
 {% include arangoshexample.html id=examplevar script=script result=result %}
 
+Alternatively, you can `truncate()` all collections of the graph if you just
+want to get rid of the data but keep the collections and graph definition.
+
 ### Remove an edge collection
 
 Delete an edge definition from the graph:

3.8/graphs-satellite-graphs-management.md

@@ -197,27 +197,31 @@ sharding for other collections (`edges`).
  {% endarangoshexample %}
  {% include arangoshexample.html id=examplevar script=script result=result %}
 
-You may drop the complete graph, but remember to drop collections that you
-might have removed from the graph beforehand, as they will not be part of the
-graph definition anymore and thus not be dropped for you. Alternatively, you
-can `truncate` the graph if you just want to get rid of the data.
+You may drop the complete graph including the underlying collections by setting
+the second argument in the call to `_drop()` to `true`. This will only drop
+collections that are in the graph definition at that point. Remember to manually
+drop collections that you might have removed from the graph beforehand.
 
  {% arangoshexample examplevar="examplevar" script="script" result="result" %}
  @startDocuBlockInline satelliteGraphManagementModify5_cluster
  @EXAMPLE_ARANGOSH_OUTPUT{satelliteGraphManagementModify5_cluster}
  var graph_module = require("@arangodb/satellite-graph");
  var relation = graph_module._relation("edges", "vertices", "vertices");
  var graph = graph_module._create("myGraph", [relation], []);
- graph._deleteEdgeDefinition("edges");
- graph._removeVertexCollection("vertices");
- graph_module._drop("myGraph", true); // does not drop any collections
+ graph._deleteEdgeDefinition("edges"); // Remove edge collection from graph definition
+ graph._removeVertexCollection("vertices"); // Remove vertex collection from graph definition
+ graph_module._drop("myGraph", true); // Does not drop any collections because none are left in the graph definition
+ // Manually clean up the collections that were left behind
  db._drop("edges"); // drop before sharding-defining 'vertices' collection
  db._drop("vertices");
  @END_EXAMPLE_ARANGOSH_OUTPUT
  @endDocuBlock satelliteGraphManagementModify5_cluster
  {% endarangoshexample %}
  {% include arangoshexample.html id=examplevar script=script result=result %}
 
+Alternatively, you can `truncate()` all collections of the graph if you just
+want to get rid of the data but keep the collections and graph definition.
+
 ### Remove an edge collection
 
 Delete an edge definition from the graph:

3.8/graphs-smart-graphs-management.md

@@ -221,27 +221,31 @@ sharding for other collections (`edges`).
 {% endarangoshexample %}
 {% include arangoshexample.html id=examplevar script=script result=result %}
 
-You may drop the complete graph, but remember to drop collections that you
-might have removed from the graph beforehand, as they will not be part of the
-graph definition anymore and thus not be dropped for you. Alternatively, you
-can `truncate` the graph if you just want to get rid of the data.
+You may drop the complete graph including the underlying collections by setting
+the second argument in the call to `_drop()` to `true`. This will only drop
+collections that are in the graph definition at that point. Remember to manually
+drop collections that you might have removed from the graph beforehand.
 
 {% arangoshexample examplevar="examplevar" script="script" result="result" %}
  @startDocuBlockInline smartGraphModify5_cluster
  @EXAMPLE_ARANGOSH_OUTPUT{smartGraphModify5_cluster}
  var graph_module = require("@arangodb/smart-graph");
  var relation = graph_module._relation("edges", "vertices", "vertices");
  var graph = graph_module._create("myGraph", [relation], [], {smartGraphAttribute: "region", numberOfShards: 9});
- graph._deleteEdgeDefinition("edges");
- graph._removeVertexCollection("vertices");
- graph_module._drop("myGraph", true); // does not drop any collections
+ graph._deleteEdgeDefinition("edges"); // Remove edge collection from graph definition
+ graph._removeVertexCollection("vertices"); // Remove vertex collection from graph definition
+ graph_module._drop("myGraph", true); // Does not drop any collections because none are left in the graph definition
+ // Manually clean up the collections that were left behind
  db._drop("edges"); // drop before sharding-defining 'vertices' collection
  db._drop("vertices");
  @END_EXAMPLE_ARANGOSH_OUTPUT
  @endDocuBlock smartGraphModify5_cluster
 {% endarangoshexample %}
 {% include arangoshexample.html id=examplevar script=script result=result %}
 
+Alternatively, you can `truncate()` all collections of the graph if you just
+want to get rid of the data but keep the collections and graph definition.
+
 ### Remove an edge collection
 
 Delete an edge definition from the graph:

3.9/graphs-satellite-graphs-management.md

@@ -197,27 +197,31 @@ sharding for other collections (`edges`).
  {% endarangoshexample %}
  {% include arangoshexample.html id=examplevar script=script result=result %}
 
-You may drop the complete graph, but remember to drop collections that you
-might have removed from the graph beforehand, as they will not be part of the
-graph definition anymore and thus not be dropped for you. Alternatively, you
-can `truncate` the graph if you just want to get rid of the data.
+You may drop the complete graph including the underlying collections by setting
+the second argument in the call to `_drop()` to `true`. This will only drop
+collections that are in the graph definition at that point. Remember to manually
+drop collections that you might have removed from the graph beforehand.
 
  {% arangoshexample examplevar="examplevar" script="script" result="result" %}
  @startDocuBlockInline satelliteGraphManagementModify5_cluster
  @EXAMPLE_ARANGOSH_OUTPUT{satelliteGraphManagementModify5_cluster}
  var graph_module = require("@arangodb/satellite-graph");
  var relation = graph_module._relation("edges", "vertices", "vertices");
  var graph = graph_module._create("myGraph", [relation], []);
- graph._deleteEdgeDefinition("edges");
- graph._removeVertexCollection("vertices");
- graph_module._drop("myGraph", true); // does not drop any collections
+ graph._deleteEdgeDefinition("edges"); // Remove edge collection from graph definition
+ graph._removeVertexCollection("vertices"); // Remove vertex collection from graph definition
+ graph_module._drop("myGraph", true); // Does not drop any collections because none are left in the graph definition
+ // Manually clean up the collections that were left behind
  db._drop("edges"); // drop before sharding-defining 'vertices' collection
  db._drop("vertices");
  @END_EXAMPLE_ARANGOSH_OUTPUT
  @endDocuBlock satelliteGraphManagementModify5_cluster
  {% endarangoshexample %}
  {% include arangoshexample.html id=examplevar script=script result=result %}
 
+Alternatively, you can `truncate()` all collections of the graph if you just
+want to get rid of the data but keep the collections and graph definition.
+
 ### Remove an edge collection
 
 Delete an edge definition from the graph:

3.9/graphs-smart-graphs-management.md

@@ -226,27 +226,31 @@ sharding for other collections (`edges`).
 {% endarangoshexample %}
 {% include arangoshexample.html id=examplevar script=script result=result %}
 
-You may drop the complete graph, but remember to drop collections that you
-might have removed from the graph beforehand, as they will not be part of the
-graph definition anymore and thus not be dropped for you. Alternatively, you
-can `truncate` the graph if you just want to get rid of the data.
+You may drop the complete graph including the underlying collections by setting
+the second argument in the call to `_drop()` to `true`. This will only drop
+collections that are in the graph definition at that point. Remember to manually
+drop collections that you might have removed from the graph beforehand.
 
 {% arangoshexample examplevar="examplevar" script="script" result="result" %}
  @startDocuBlockInline smartGraphModify5_cluster
  @EXAMPLE_ARANGOSH_OUTPUT{smartGraphModify5_cluster}
  var graph_module = require("@arangodb/smart-graph");
  var relation = graph_module._relation("edges", "vertices", "vertices");
  var graph = graph_module._create("myGraph", [relation], [], {smartGraphAttribute: "region", numberOfShards: 9});
- graph._deleteEdgeDefinition("edges");
- graph._removeVertexCollection("vertices");
- graph_module._drop("myGraph", true); // does not drop any collections
+ graph._deleteEdgeDefinition("edges"); // Remove edge collection from graph definition
+ graph._removeVertexCollection("vertices"); // Remove vertex collection from graph definition
+ graph_module._drop("myGraph", true); // Does not drop any collections because none are left in the graph definition
+ // Manually clean up the collections that were left behind
  db._drop("edges"); // drop before sharding-defining 'vertices' collection
  db._drop("vertices");
  @END_EXAMPLE_ARANGOSH_OUTPUT
  @endDocuBlock smartGraphModify5_cluster
 {% endarangoshexample %}
 {% include arangoshexample.html id=examplevar script=script result=result %}
 
+Alternatively, you can `truncate()` all collections of the graph if you just
+want to get rid of the data but keep the collections and graph definition.
+
 ### Remove an edge collection
 
 Delete an edge definition from the graph: