Soften some wording

docs/source/cpp/dataset.rst

@@ -395,11 +395,11 @@ cardinality 1,000 will make that 365,365 calls.
 
 The most optimal partitioning layout will depend on your data, access patterns, and which
 systems will be reading the data. Most systems, including Arrow, should work across a 
-range of file sizes and partitioning layouts, but there are extremes you should avoid. To 
-avoid worst case behavior, keep to these guidelines:
+range of file sizes and partitioning layouts, but there are extremes you should avoid. These
+guidelines can help avoid some known worst cases:
 
- * Avoid files smaller than 20MB and larger than 2GB
- * Avoid partitioning layouts with more than 10,000 distinct partitions.
+* Avoid files smaller than 20MB and larger than 2GB.
+* Avoid partitioning layouts with more than 10,000 distinct partitions.
 
 For file formats that have a notion of groups within a file, such as Parquet, similar
 guidelines apply. Row groups can provide parallelism when reading and allow data skipping

docs/source/python/dataset.rst

@@ -602,11 +602,11 @@ cardinality 1,000 will make that 365,365 calls.
 
 The most optimal partitioning layout will depend on your data, access patterns, and which
 systems will be reading the data. Most systems, including Arrow, should work across a 
-range of file sizes and partitioning layouts, but there are extremes you should avoid. To 
-avoid worst case behavior, keep to these guidelines:
+range of file sizes and partitioning layouts, but there are extremes you should avoid. These
+guidelines can help avoid some known worst cases:
 
- * Avoid files smaller than 20MB and larger than 2GB
- * Avoid partitioning layouts with more than 10,000 distinct partitions.
+* Avoid files smaller than 20MB and larger than 2GB.
+* Avoid partitioning layouts with more than 10,000 distinct partitions.
 
 For file formats that have a notion of groups within a file, such as Parquet, similar
 guidelines apply. Row groups can provide parallelism when reading and allow data skipping

r/vignettes/dataset.Rmd

@@ -448,10 +448,10 @@ cardinality 1,000 will make that 365,365 calls.
 
 The most optimal partitioning layout will depend on your data, access patterns, and which
 systems will be reading the data. Most systems, including Arrow, should work across a 
-range of file sizes and partitioning layouts, but there are extremes you should avoid. To 
-avoid worst case behavior, keep to these guidelines:
+range of file sizes and partitioning layouts, but there are extremes you should avoid. These
+guidelines can help avoid some known worst cases:
 
- * Avoid files smaller than 20MB and larger than 2GB
+ * Avoid files smaller than 20MB and larger than 2GB.
  * Avoid partitioning layouts with more than 10,000 distinct partitions.
 
 For file formats that have a notion of groups within a file, such as Parquet, similar