diff --git a/doc/source/admin/special_topics/mulled_containers.rst b/doc/source/admin/special_topics/mulled_containers.rst
index 213b2b08167..28191842d94 100644
--- a/doc/source/admin/special_topics/mulled_containers.rst
+++ b/doc/source/admin/special_topics/mulled_containers.rst
@@ -25,7 +25,7 @@ requirement field.
 This approach has shown two limitations that slowed down the adoption by tool developers.
 First, every tool needs to be annotated with a container name (as shown above) and this container needs
 to be created beforehand, usually manually. The second reason is that Galaxy tools should be deployable everywhere,
-independent of the underlying system, meaning if Docker is not available Galaxy should use Conda packages. 
+regardless of the underlying system, meaning that if Docker is not available, Galaxy should use Conda packages instead. 
 This puts an additional burden on tool developers who need to take care of two dependency resolvers. This setup can cause
 different tool results depending on the resolver, because both the Conda package and the Docker container are
 usually not created out of the same recipe and maybe were compiled in a different way, use different sources etc.