capitalization

Author: nsheff

docs/decision_record.md

@@ -414,15 +414,15 @@ Adding prefixes will complicate things and does not add benefits. Prefixes may b
 - <https://github.com/ga4gh/refget/issues/37>
 
 
-## 2023-06-28 - SeqCol JSON schema defines reserved attributes without additional namespacing
+## 2023-06-28 - Seqcol JSON schema defines reserved attributes without additional namespacing
 
 ### Decision
 
 One potential issue may arise if a custom implementation uses an attribute that a future version of seqcol adds to the schema, and if these attributes are defined differently. This will create a name clash and the custom implementation wouldn't be compatible with the future seqcol schema. It would be nice to prevent such future clashes, which would require ensuring that future seqcol attributes mean the same thing across collections so they are compatible. One way to solve this would be to define an namespace reserved by the specification, so that custom attributes look different and will therefore guarantee that custom attribute never clashes with seqcol attributes, thereby ensuring that custom implementations will be compatible with any future schema updates.
 
 Despite the potential issue for custom attribute clashes, we decided:
 
-1. We will not use any additional namespacing. Instead, the SeqCol schema declares and defines the specific attributes of a sequence collection. We will "claim" any reserved keywords in the secqol schema we publish, not by defining a style or namespace of reserved keywords.
+1. We will not use any additional namespacing. Instead, the seqcol schema declares and defines the specific attributes of a sequence collection. We will "claim" any reserved keywords in the secqol schema we publish, not by defining a style or namespace of reserved keywords.
 
 2. We will try to add to this many things that we forsee as possible attributes that could be defined in a seqcol. Thus, we will provide an official set of definitions that should prevent many possible future clashes.
 

docs/seqcols/compare_collections.md

@@ -12,7 +12,7 @@ You can also `POST` a local collection to `/comparison/:digest1` to compare it t
 The comparison function gives information-rich feedback about the two collections, but it can take some thought to interpret.
 Here are some examples.
 
-The best way is to use the Refget [SeqCol Comparison Interpretation Module (SCIM)](https://refget.databio.org/scim/).
+The best way is to use the Refget [Seqcol Comparison Interpretation Module (SCIM)](https://refget.databio.org/scim/).
 You paste in the JSON output of a comparison, and it provides an interpretation for you.
 
 ## Interpretation details

mkdocs.yml

@@ -8,7 +8,7 @@ nav:
     - Sequences: sequences/README.md
     - Sequence Collections: seqcols/README.md
   - Detailed how-to guides:
-    - Compute a digest given a SeqCol: seqcols/digest_from_collection.md
+    - Compute a digest given a seqcol: seqcols/digest_from_collection.md
     - Compare two sequence collections: seqcols/compare_collections.md
   - Implementations:
     - Python: implementation_python.md