Update readme for service account

README.md

@@ -29,7 +29,7 @@ Starting a container is a blocking call that will wait until it results in a run
 
 By default, all containers will be orchestrated using kubernetes Deployment resources. However, in some cases it could make more sense to deploy the container as a Job instead. The deployment resource type can be forced by adding a `com.joyrex2001.kubedock.deploy-as-job` label that contains `true` on the container that should be orchestrated as a Job instead. This can also be set globally with the `--deploy-as-job` argument, which will result in all containers being deployes as Jobs. The restart policy for Jobs is fixed to `OnFailure`.
 
-The containers will be started with the `default` service account. This can be changed with the `--service-acount` argument, as well by adding a `com.joyrex2001.kubedock.service-account` label containing the service account to be used. If required, the uid of the user that runs inside the container can also be enforced with the `--runas-user` argument and the `com.joyrex2001.kubedock.runas-user` label.
+The containers will be started with the `default` service account. This can be changed with the `--service-acount`. If required, the uid of the user that runs inside the container can also be enforced with the `--runas-user` argument and the `com.joyrex2001.kubedock.runas-user` label.
 
 ## Volumes