diff --git a/dandiapi/api/copy.py b/dandiapi/api/copy.py
index d974732c8..2d4c03daf 100644
--- a/dandiapi/api/copy.py
+++ b/dandiapi/api/copy.py
@@ -48,7 +48,7 @@ class CopyObjectPart:
     dest_key: str
 
     # Whether or not to include the byte range in the request
-    # (exlcuded for single part copies)
+    # (excluded for single part copies)
     include_range: bool = True
 
     @property
diff --git a/dandiapi/api/views/dandiset.py b/dandiapi/api/views/dandiset.py
index 5da2c6c13..9e53a8ea5 100644
--- a/dandiapi/api/views/dandiset.py
+++ b/dandiapi/api/views/dandiset.py
@@ -203,7 +203,7 @@ def _get_dandiset_to_version_map(dandisets):
         for version in versions:
             version: Version
 
-            # Annnotate with total size and asset count (with default)
+            # Annotate with total size and asset count (with default)
             stats = version_stats.get(version.id, {'total_size': 0, 'num_assets': 0})
             version.total_size = stats['total_size']
             version.num_assets = stats['num_assets']
diff --git a/doc/design/publish-1.md b/doc/design/publish-1.md
index 82265df61..e6fb2c67f 100644
--- a/doc/design/publish-1.md
+++ b/doc/design/publish-1.md
@@ -116,7 +116,7 @@ This involves digesting the Version metadata into something that can be used by
 See the doi-generation-1.md design document for more details.
 
 4. For every draft Asset in the draft Version, the required publish metadata fields are injected, turning those Assets into published Assets.
-Published Assets, e.g. Asssets that already have those fields from previous publishes, _are skipped_.
+Published Assets, e.g. Assets that already have those fields from previous publishes, _are skipped_.
 Because they describe Assets that have already been published in a past version, there is no reason to re-publish them.
 
 5. Associate all of the publish Assets, new and old, with the new published Version.