Edited 300_Aggregations/125_Conclusion.asciidoc with Atlas code editor

Author: skalapurakkel

300_Aggregations/125_Conclusion.asciidoc

@@ -25,7 +25,7 @@ so that it is memory-friendly
 - During indexing, by configuring heavy fields to use disk-based doc values instead
 of in-memory fielddata
 - At search time, by utilizing approximate aggregations and data filtering
-- At a node level, by setting hard memory limits and dynamic circuit-breaker limits
+- At a node level, by setting hard memory and dynamic circuit-breaker limits
 - At an operations level, by monitoring memory usage and controlling slow garbage-collection cycles, potentially by adding more nodes to the cluster
 
 Most deployments will use one or more of the preceding methods.  The exact combination
@@ -40,4 +40,4 @@ six months or one year as your data grows. What methods will you use to continue
 scaling?
 
 It is better to plan out these life cycles of your cluster ahead of time, rather
-than panicking at 3 a.m. because your cluster is at 90% heap utilization.
+than panicking at 3 a.m. because your cluster is at 90% heap utilization.