improve some doc cohesion and fix generator->definitions README link (m…

…edplum#3373)
dillonstreator · Nov 25, 2023 · bdb0d6a · bdb0d6a
1 parent 3eabd3b
commit bdb0d6a
Show file tree

Hide file tree

Showing 4 changed files with 6 additions and 6 deletions.
diff --git a/packages/docs/docs/fhir-datastore/migration-logic.md b/packages/docs/docs/fhir-datastore/migration-logic.md
@@ -23,7 +23,7 @@ When considering which option is best for you, we must consider some system char
 - How easy or difficult is it to modify the existing system?
  - Are engineers actively updating the existing system?
  - How frequently does the existing system deploy new releases?
- - Is the existing system stable, or are changes avoided?
+ - Is the existing system stable, or is change frequent?
 - How easy or difficult is it to programmatically access the existing system?
  - Is there an API?
  - Is the API accessible on the open internet?

diff --git a/packages/docs/docs/fhir-datastore/patient-deduplication/merging.mdx b/packages/docs/docs/fhir-datastore/patient-deduplication/merging.mdx
@@ -83,9 +83,9 @@ Over time, you may find that two master records actually correspond to the same
 - You accumulate more precise data from your source systems.
 - Your matching rules become more advanced.
 
-A key design question will whether your automated pipelines are allowed to combine or split master records after they have been created.
+A key design question will be whether your automated pipelines are allowed to combine or split master records after they have been created.
 
-The benefit of automated splitting/merging that your target system always maintains the most accurate master records.
+The benefit of automated splitting/merging is that your target system always maintains the most accurate master records.
 
 The drawback is that frequently combining and splitting master records can cause instability in downstream systems. This can happen in the early days of pipeline development, when matching and merge rules are still being finalized.
 
@@ -102,7 +102,7 @@ The two options are:
 
 ![rewrite references](./rewrite-references.png)
 
-The tradeoff primary will be dictated by the downstream applications and the frequency of unmerge operations.
+The downstream applications and the frequency of unmerge operations will primarily dictate the tradeoffs.
 
 ### Rewriting references to master record
 

diff --git a/packages/docs/docs/fhir-datastore/patient-deduplication/patient-deduplication.md b/packages/docs/docs/fhir-datastore/patient-deduplication/patient-deduplication.md
@@ -4,7 +4,7 @@ sidebar_position: 8
 
 # Patient Deduplication Architectures
 
-Deduplicating patient records from multiple sources is a nuanced workflow. We've put together this this guide to go over the basics of merging patient records, and review some of the most important technical design considerations when building a patient deduplication pipeline. The pipeline described here is the basis of an [Enterprise Master Patient Index](https://en.wikipedia.org/wiki/Enterprise_master_patient_index) (EMPI).
+Deduplicating patient records from multiple sources is a nuanced workflow. We've put this guide together to go over the basics of merging patient records, and review some of the most important technical design considerations when building a patient deduplication pipeline. The pipeline described here is the basis of an [Enterprise Master Patient Index](https://en.wikipedia.org/wiki/Enterprise_master_patient_index) (EMPI).
 
 We've organized the guide as follows:
 

diff --git a/packages/generator/README.md b/packages/generator/README.md
@@ -8,4 +8,4 @@ Run the generator:
 npm run generate
 ```
 
-See the [definitions](../packages/definitions/README.md) for more details.
+See the [definitions](../definitions/README.md) for more details.