From 2750a9e6c44a7a5dedecca9f7a0c14f74e49dd82 Mon Sep 17 00:00:00 2001 From: Jonathan Shook Date: Thu, 21 Nov 2024 15:36:39 -0600 Subject: [PATCH] typos --- .../adapters/api/activityimpl/uniform/DriverAdapter.java | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nb-apis/adapters-api/src/main/java/io/nosqlbench/adapters/api/activityimpl/uniform/DriverAdapter.java b/nb-apis/adapters-api/src/main/java/io/nosqlbench/adapters/api/activityimpl/uniform/DriverAdapter.java index 449231dbc..563e2fb0a 100644 --- a/nb-apis/adapters-api/src/main/java/io/nosqlbench/adapters/api/activityimpl/uniform/DriverAdapter.java +++ b/nb-apis/adapters-api/src/main/java/io/nosqlbench/adapters/api/activityimpl/uniform/DriverAdapter.java @@ -65,7 +65,7 @@ import java.util.function.LongFunction; /// /// or in another way, simply `opExecution(opFunction(cycle))`. /// -/// This is a simplified view of the detailed steps, most of which are handled automatically by the nosqlbench engine: +/// This is a simplified view of the detailed steps, many of which are handled automatically by the nosqlbench engine: /// /// ``` /// cycle value @@ -78,7 +78,7 @@ import java.util.function.LongFunction; /// -> op execution ///``` /// -/// Notice that all of the stages are optimized via a form of memoization. This is a side-effect of forcing the +/// Notice that some stages are optimized via a form of memoization. This is a side-effect of forcing the /// initialization of the op construction pipelines into lamda form, where unchanging initialization data is captured /// explicitly or by reference in closures. This works in our favor for performance, since these lambdas are /// optimized and executed very efficiently within modern Java VMs.