YosiSF · rishabh96b · Aug 22, 2020 · Jan 24, 2022
diff --git a/.DS_Store b/.DS_Store
diff --git a/.gradle/7.1.1/dependencies-accessors/dependencies-accessors.lock b/.gradle/7.1.1/dependencies-accessors/dependencies-accessors.lock
diff --git a/.gradle/7.1.1/dependencies-accessors/gc.properties b/.gradle/7.1.1/dependencies-accessors/gc.properties
diff --git a/.gradle/7.1.1/executionHistory/executionHistory.lock b/.gradle/7.1.1/executionHistory/executionHistory.lock
diff --git a/.gradle/7.1.1/fileChanges/last-build.bin b/.gradle/7.1.1/fileChanges/last-build.bin
diff --git a/.gradle/7.1.1/fileHashes/fileHashes.lock b/.gradle/7.1.1/fileHashes/fileHashes.lock
diff --git a/.gradle/7.1.1/gc.properties b/.gradle/7.1.1/gc.properties
diff --git a/.gradle/buildOutputCleanup/buildOutputCleanup.lock b/.gradle/buildOutputCleanup/buildOutputCleanup.lock
diff --git a/.gradle/buildOutputCleanup/cache.properties b/.gradle/buildOutputCleanup/cache.properties
@@ -1,2 +1,2 @@
-#Mon Aug 03 09:08:27 PDT 2020
-gradle.version=6.1.1
+#Sun Jan 23 03:18:45 PST 2022
+gradle.version=7.1.1
diff --git a/README.md b/README.md
@@ -1,10 +1,10 @@
-EinsteinDB is an embedded knwoledge base on relativistic sidecars: multi-consumer, multi-producer; console agnostic HTAP.
+EinsteinDB is an embedded knowledge base on relativistic sidecars: multi-consumer, multi-producer; console agnostic HTAP.
 
 EinsteinDB as presented herein is a community edition DB-a-a-S built with Rust, Haskell, Docker, Kubernetes, Ansible and ❤️ 
-Along with MilevaDB, both components make up a cost-optimized distributed-SQL cluster with prolog querying, proto-buff generating, and regular
-expression querying of Cold, Warm, and Hot Data Chunks. EinsteinDB implements a two-pronged Append-Merge Pull mechanism (similar to git). Because of EinsteinDB's Homomorphic Keyspace, MilevaDB can transmute key-value pairs as lock-free version-sharing secondary indices but for dirty pages pointing to trees. We define an einstein_merkle tree as the BtreeMapEngine invariant (or the HashMap) for B+Trees but guaranteeing better read-heavy throughpu.
+Along with MilevaDB, both components make up a cost-optimized distributed-SQL cluster with prolog querying, protobuf generating, and regular
+expression querying of Cold, Warm, and Hot Data Chunks. EinsteinDB implements a two-pronged Append-Merge Pull mechanism (similar to git). Because of EinsteinDB's Homomorphic Keyspace, MilevaDB can transmute key-value pairs as lock-free version-sharing secondary indices but for dirty pages pointing to trees. We define an einstein_merkle tree as the BtreeMapEngine invariant (or the HashMap) for B+Trees but guaranteeing better read-heavy throughput.
 
-EinsteinDB and MilevaDB interact with SQLite(at the top layer), PostgresQL for persistence(middle layer), and LMDB's Iterator implementation (bottom layer). Designed for Write-Optimized Copy-on-Write Semantics, Repeatable Read isolation guarantees for HTAP, column cracking, and vectorized SIMD for OLAP/OLTP SparkQL streams. VioletaBFT is EinsteinDB's distributed consensus protocol implemented with Haskell.
+EinsteinDB and MilevaDB interact with SQLite(at the top layer), PostgreSQL for persistence(middle layer), and LMDB's Iterator implementation (bottom layer). Designed for Write-Optimized Copy-on-Write Semantics, Repeatable Read isolation guarantees for HTAP, column cracking, and vectorized SIMD for OLAP/OLTP SparkQL streams. VioletaBFT is EinsteinDB's distributed consensus protocol implemented with Haskell.
 
 VioletaBFT is a Byzantine Fault Tolerant HoneyBadger/Raft protocol which provides consistency guarantees and maintains consensus between replicas. Unlike most of the competitors, VioletaBFT compiles to Rust (From Haskell) and pipelines a JIT Automatic failover with Partition persistence.
 
diff --git a/Users:tyco:Downloads:mentat.textClipping b/Users:tyco:Downloads:mentat.textClipping