diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
index 53565e3a..43122b6e 100644
--- a/.pre-commit-config.yaml
+++ b/.pre-commit-config.yaml
@@ -1,6 +1,6 @@
 repos:
 -   repo: https://github.com/codespell-project/codespell
-    rev: v2.2.5
+    rev: v2.2.6
     hooks:
     -   id: codespell
 -   repo: https://github.com/psf/black
@@ -19,12 +19,12 @@ repos:
     -   id: end-of-file-fixer
     -   id: check-yaml
 -   repo: https://github.com/asottile/pyupgrade
-    rev: v3.13.0
+    rev: v3.14.0
     hooks:
     -   id: pyupgrade
         args:  [--py37-plus]
 -   repo: https://github.com/asottile/reorder-python-imports
-    rev: v3.11.0
+    rev: v3.12.0
     hooks:
     -   id: reorder-python-imports
         args: ['--application-directories=execnet', --py37-plus]
diff --git a/CHANGELOG.rst b/CHANGELOG.rst
index 3776bad1..a0f0d67a 100644
--- a/CHANGELOG.rst
+++ b/CHANGELOG.rst
@@ -130,7 +130,7 @@
   (this also fixes the bpython interaction issues)
 
 - Fix issue38: provide ability to connect to Vagrant VMs easily
-  using :code:`vagrant_ssh=defaut` or :code:`vagrant_ssh=machinename`
+  using :code:`vagrant_ssh=default` or :code:`vagrant_ssh=machinename`
   this feature is experimental and will be refined in future releases.
   Thanks Christian Theune for the discussion and the initial pull request.
 
@@ -432,7 +432,7 @@
 
 * make internal protocols more robust against serialization failures
 
-* fix a seralization bug with nested tuples containing empty tuples
+* fix a serialization bug with nested tuples containing empty tuples
   (thanks to ronny for discovering it)
 
 * setting the environment variable EXECNET_DEBUG will generate per
diff --git a/doc/example/test_proxy.rst b/doc/example/test_proxy.rst
index 0a90f258..a4f45f37 100644
--- a/doc/example/test_proxy.rst
+++ b/doc/example/test_proxy.rst
@@ -7,7 +7,7 @@ Simple Proxying
 Using the via arg of specs we can create a gateway
 whose io is created on a remote gateway and proxied to the master.
 
-The simlest use case, is where one creates one master process
+The simplest use case, is where one creates one master process
 and uses it to control new workers and their environment
 
 ::