diff --git a/doc/usage/extensions/autosummary.rst b/doc/usage/extensions/autosummary.rst
index c84dcb60eff..3b993348a78 100644
--- a/doc/usage/extensions/autosummary.rst
+++ b/doc/usage/extensions/autosummary.rst
@@ -107,7 +107,7 @@ The :mod:`sphinx.ext.autosummary` extension does this in two parts:
       How to display signatures. Valid values are
 
       - ``long`` (*default*): use a long signature. This is still cut off so that name
-        plus signature do not exceeed a certain length.
+        plus signature do not exceed a certain length.
       - ``short``: Function and class signatures are displayed as ``(…)`` if they have
         arguments and as ``()`` if they don't have arguments.
       - ``none``: do not show signatures.
diff --git a/doc/usage/restructuredtext/directives.rst b/doc/usage/restructuredtext/directives.rst
index 4b1a2042df9..92b24306e87 100644
--- a/doc/usage/restructuredtext/directives.rst
+++ b/doc/usage/restructuredtext/directives.rst
@@ -1587,7 +1587,7 @@ Check the :confval:`latex_table_style`.
    compatible with ``tabulary``.  At ``8.3.0`` a technique, which was already
    in use for merged cells, was extended to such cases, and the sole
    "problematic" contents are code-blocks and nested tables.  So tables
-   containing (only) cells with mutliple paragraphs, bullet or enumerated
+   containing (only) cells with multiple paragraphs, bullet or enumerated
    lists, or line blocks, will now better fit to their contents (if not
    rendered by ``longtable``).  Cells with object descriptions or admonitions
    will still have a tendency to induce the table to fill the full text area
@@ -1726,7 +1726,7 @@ There is this directive:
    Multiple production lists with the same *production_group*
    thus define rules in the same scope.
    This can also be used to split the description of a long or complex grammar
-   accross multiple ``productionlist`` directives with the same *production_group*.
+   across multiple ``productionlist`` directives with the same *production_group*.
 
    The definition can contain token names which are marked as interpreted text,
    (e.g. "``sum ::= `integer` "+" `integer```"),
diff --git a/sphinx/domains/std/__init__.py b/sphinx/domains/std/__init__.py
index 52ccef67c24..3afad70d60d 100644
--- a/sphinx/domains/std/__init__.py
+++ b/sphinx/domains/std/__init__.py
@@ -693,7 +693,7 @@ def make_name_target(
 
     @staticmethod
     def separator_node(*, name: str, max_len: int) -> nodes.Text:
-        """Return seperator between 'name' and 'tokens'."""
+        """Return separator between 'name' and 'tokens'."""
         if name:
             return nodes.Text(' ::= '.rjust(max_len - len(name) + 5))
         return nodes.Text(' ' * (max_len + 5))
diff --git a/sphinx/texinputs/sphinxlatextables.sty b/sphinx/texinputs/sphinxlatextables.sty
index b80cc83be8d..8320ef31cf3 100644
--- a/sphinx/texinputs/sphinxlatextables.sty
+++ b/sphinx/texinputs/sphinxlatextables.sty
@@ -148,7 +148,7 @@
     \prevdepth\z@\vskip\sphinxtablepost\relax}%
 % B. Table with tabular or tabulary
 \def\sphinxattablestart{\par
-    \ifvmode % guard agains being nested in a table cell
+    \ifvmode % guard against being nested in a table cell
       \vskip\dimexpr\sphinxtablepre\relax
     \fi
                         \spx@inframedtrue % message to sphinxheavybox
diff --git a/sphinx/writers/latex.py b/sphinx/writers/latex.py
index f204f585f6a..f92f983fbed 100644
--- a/sphinx/writers/latex.py
+++ b/sphinx/writers/latex.py
@@ -173,7 +173,7 @@ def get_table_type(self) -> str:
             # types is used.  The next test will have false positive from
             # syntax such as >{\RaggedRight} but it will catch *{3}{J} which
             # does require tabulary and would crash tabular
-            # It is user responsability not to use a tabulary column type for
+            # It is user responsibility not to use a tabulary column type for
             # a column having a problematic cell.
             if any(c in 'LRCJT' for c in self.colspec):
                 return 'tabulary'