docs: fix typo in transports.md (#1416)

smola · web-flow · commit ea624681aef9 · 2020-06-17T13:35:07.000+02:00
diff --git a/docs/transports.md b/docs/transports.md
@@ -4,7 +4,7 @@
 | | |
 |---|---|
 | Maven coordinates | `com.github.docker-java:docker-java-transport-httpclient5` |
-| Stabilitty | 🙂|
+| Stability | 🙂|
 | Long term support plans | ✅ |
 | Unix sockets support | ✅ |
 | Windows Npipe support | ✅ |
@@ -18,7 +18,7 @@ It has everything to become the default transport of docker-java in future relea
 | | |
 |---|---|
 | Maven coordinates | `com.github.docker-java:docker-java-transport-zerodep` |
-| Stabilitty | 🙂|
+| Stability | 🙂|
 | Long term support plans | ✅ |
 | Unix sockets support | ✅ |
 | Windows Npipe support | ✅ |
@@ -32,7 +32,7 @@ Note: due to the implementation details, it cannot be true "0 dependencies" modu
 | | |
 |---|---|
 | Maven coordinates | `com.github.docker-java:docker-java-transport-okhttp` |
-| Stabilitty | 🧐|
+| Stability | 🧐|
 | Long term support plans | ❓ |
 | Unix sockets support | ✅ |
 | Windows Npipe support | ✅ |
@@ -46,7 +46,7 @@ OkHttp's migration to Kotlin and the need to use internal APIs for doing stdin h
 | | |
 |---|---|
 | Maven coordinates | `com.github.docker-java:docker-java-transport-netty` |
-| Stabilitty | 🧐|
+| Stability | 🧐|
 | Long term support plans | ❌ |
 | Unix sockets support | ✅ |
 | Windows Npipe support | ❌ |
@@ -62,7 +62,7 @@ The community may decide to pick it up and continue the development as a 3rd par
 | | |
 |---|---|
 | Maven coordinates | `com.github.docker-java:docker-java-transport-jersey` |
-| Stabilitty | 🙃|
+| Stability | 🙃|
 | Long term support plans | ❌ |
 | Unix sockets support | ✅ |
 | Windows Npipe support | ❌ |
@@ -71,4 +71,4 @@ The community may decide to pick it up and continue the development as a 3rd par
 Jersey was the initial transport of the project. And, while working well, it was lacking support for connection hijacking (e.g. stdin attachment) or Windows Npipes.
 The big amount of dependencies was also causing issues.
 
-Since Apache HttpClient 5-based transport is available now, there is no reason to keep Jersey and it will eventually be removed.
+Since Apache HttpClient 5-based transport is available now, there is no reason to keep Jersey and it will eventually be removed.
