Merge pull request #847 from zinggAI/enterprisedocs

spelling corrected and added header2 issues #843
zinggAI · Jul 2, 2024 · f5ce1b2 · f5ce1b2
2 parents 9a145ed + 6692bca
commit f5ce1b2
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 5 deletions.
diff --git a/docs/deterministicMatching.md b/docs/deterministicMatching.md
@@ -1,6 +1,7 @@
-# Deterministic Matching - *Zingg Enterprise Feature*  
+
+## Deterministic Matching - *Zingg Enterprise Feature*  
 
-Zingg Enterprise allows the ability to plug rule based deterministic matching along with already Zingg AI's probabilistic matching. If the data contains sure identifiers like emails, SSNs, passport ids etc, we can use these attributes to resolve records. The deterministic matching flow is weaved into Zingg's flow to ensure that each record which has a match finds one, probabilistically, deterministcally or both. If the data has known identifiers, Zingg Enterprise's deterministic matching highly improves both matching accuracy and performance.  
+Zingg Enterprise allows the ability to plug rule based deterministic matching along with already Zingg AI's probabilistic matching. If the data contains sure identifiers like emails, SSNs, passport ids etc, we can use these attributes to resolve records. The deterministic matching flow is weaved into Zingg's flow to ensure that each record which has a match finds one, probabilistically, deterministically or both. If the data has known identifiers, Zingg Enterprise's deterministic matching highly improves both matching accuracy and performance.  
 
 ## Example for configuring it in json:  
 ```json  

diff --git a/docs/runIncremental.md b/docs/runIncremental.md
@@ -1,6 +1,7 @@
-# Run Incremental Loads For New and Updated Records - *Zingg Enterprise Feature*  
+
+## Run Incremental Loads For New and Updated Records - *Zingg Enterprise Feature*  
 
-Rerunning matching on entire datasets is wasteful, and we lose the lineage of matched records against a persistent identifier. Using Zingg Enterprise, incremental loads can be run to match existing pre resolved entities. The new and updated records are matched to existing clusters, and new persistent ZINGG_IDs generated for records which do not find a match. If a record gets updated and Zingg Enterprise discovers that it is a more suitable match with another cluster, it will be reassigned. Cluster assignment, merge and unmerge happens automatically in the flow. Zingg Entperirse also takes care of human feedback on previously matched data to ensure that it doesnt override the approved records.   
+Rerunning matching on entire datasets is wasteful, and we lose the lineage of matched records against a persistent identifier. Using Zingg Enterprise, incremental loads can be run to match existing pre resolved entities. The new and updated records are matched to existing clusters, and new persistent ZINGG_IDs generated for records which do not find a match. If a record gets updated and Zingg Enterprise discovers that it is a more suitable match with another cluster, it will be reassigned. Cluster assignment, merge and unmerge happens automatically in the flow. Zingg Enterprise also takes care of human feedback on previously matched data to ensure that it does not override the approved records.   
 
 ## The incremental phase is run as follows:  
 `./scripts/zingg.sh --phase runIncremental --conf <location to incrementalConf.json>`  
@@ -24,7 +25,7 @@ Rerunning matching on entire datasets is wasteful, and we lose the lineage of ma
 }  
 ```
 
-## runIncremental can also be triggerred using python by invoking:  
+## runIncremental can also be triggered using python by invoking:  
 `./scripts/zingg.sh --run examples/FebrlExample.py`  
 
 ### Python code example: