fix: resolve typos

ga4gh · Jan 8, 2025 · ccd9b8b · ccd9b8b
1 parent adfbe3c
commit ccd9b8b
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/docs/source/appendices/design_decisions.rst b/docs/source/appendices/design_decisions.rst
@@ -10,7 +10,7 @@ GA4GH Inherent Properties over Value Objects
 
 In VRS 1.0 we operated under the principle that all identifiable objects in VRS (e.g. Allele, SequenceLocation, etc.)
 would be *value objects*. This meant that they should be immutable and contain only required fields that are
-necessary to uniquely identify the object. This approach somewhat simplified the ability to genertate the digests by
+necessary to uniquely identify the object. This approach somewhat simplified the ability to generate the digests by
 allowing the computation of the digest to be based on the entire object. An exception was made for properties with a
 leading underscore (namely, the *_id* property), which was removed from the object before a digest was calculated.
 

diff --git a/docs/source/conventions/computed_identifiers.rst b/docs/source/conventions/computed_identifiers.rst
@@ -266,8 +266,8 @@ However, as described here, these identifiers are dependent upon the structure o
 the identifier is constructed. Consequently, there is no guarantee that VRS computed identifiers will
 remain stable across major version releases of VRS; for example, all VRS v1.x computed identifiers are
 distinct from all VRS v2.x identifiers. It is recommended that implementers heed the maturity level of
-data classes as defined by the :ref:`maturity-model` when gauging the stability of data classes–and
-therefore object identifiers from thoses classes–across releases of VRS.
+data classes as defined by the :ref:`maturity-model` when gauging the stability of data classes-and
+therefore object identifiers from those classes-across releases of VRS.
 
 References
 @@@@@@@@@@