codespell

atproto/lexicon/catalog.go

···
 
 // Interface type for a resolver or container of lexicon schemas, and methods for validating generic data against those schemas.
 type Catalog interface {
-	// Looks up a schema refrence (NSID string with optional fragment) to a Schema object.
+	// Looks up a schema reference (NSID string with optional fragment) to a Schema object.
 	Resolve(ref string) (*Schema, error)
 }
 

atproto/lexicon/lexicon.go

···
 	StrictRecursiveValidation
 )
 
-// Combination of agument flags for less formal validation. Recommended for, eg, working with old/legacy data from 2023.
+// Combination of argument flags for less formal validation. Recommended for, eg, working with old/legacy data from 2023.
 var LenientMode ValidateFlags = AllowLegacyBlob | AllowLenientDatetime
 
 // Represents a Lexicon schema definition

atproto/lexicon/testdata/catalog/query.json

···
   "lexicon": 1,
   "id": "example.lexicon.query",
   "revision": 1,
-  "description": "exersizes many lexicon features for the query type",
+  "description": "exercizes many lexicon features for the query type",
   "defs": {
     "main": {
       "type": "query",

atproto/lexicon/testdata/catalog/record.json

···
   "lexicon": 1,
   "id": "example.lexicon.record",
   "revision": 1,
-  "description": "exersizes many lexicon features for the record type",
+  "description": "exercizes many lexicon features for the record type",
   "defs": {
     "main": {
       "type": "record",

atproto/repo/mst/encoding.go

···
 	return &nd, nil
 }
 
-// Transforms `Node` stuct to `NodeData`, which is the format used for encoding to CBOR.
+// Transforms `Node` struct to `NodeData`, which is the format used for encoding to CBOR.
 //
 // Will panic if any entries are missing a CID (must compute those first)
 func (n *Node) NodeData() NodeData {

cmd/collectiondir/README.md

···
 
 `listCollections` returns JSON with a map of collection name to approximate number of dids implementing it.
 With no `c` parameter it returns all known collections with cursor paging.
-With up to 20 repeated `c` paramaters it returns only those collections (no paging).
+With up to 20 repeated `c` parameters it returns only those collections (no paging).
 It may be the cached result of a computation, up to several minutes out of date.
 ```json
 {"collections":{"app.bsky.feed.post": 123456789, "some collection": 42},
···
 it then calls the collection directory for a list of repos which may have already created data in this collection,
 and does `getRepo` calls to those repo's PDSes to get prior data.
 By the time it is done paging forward through the collection directory results and getting those repos,
-it will have backfilled data and new data it has collected live off the firehose.
+it will have backfilled data and new data it has collected live off the firehose.

cmd/collectiondir/serve.go

···
 }
 
 // return cached collection stats if they're fresh
-// return new collection stats if they can be calculated quicly
+// return new collection stats if they can be calculated quickly
 // return stale cached collection stats if new stats take too long
 // just wait for fresh stats if there are no cached stats
 // stalenessAllowed is how old stats can be before we try to recalculate them, 0=default of 5 minutes