Add cap-add for IPC_LOCK to dev example as well

vault/content.md

@@ -26,7 +26,7 @@ The container has a Vault configuration directory set up at `/vault/config` and
 ## Running Vault for Development
 
 ```console
-$ docker run -d --name=dev-vault vault
+$ docker run --cap-add=IPC_LOCK -d --name=dev-vault vault
 ```
 
 This runs a completely in-memory Vault server, which is useful for development but should not be used in production.
@@ -39,13 +39,13 @@ When running in development mode, two additional options can be set via environm
 As an example:
 
 ```console
-$ docker run -e 'VAULT_DEV_ROOT_TOKEN_ID=myroot' -e 'VAULT_DEV_LISTEN_ADDRESS=127.0.0.1:1234' vault
+$ docker run --cap-add=IPC_LOCK -e 'VAULT_DEV_ROOT_TOKEN_ID=myroot' -e 'VAULT_DEV_LISTEN_ADDRESS=127.0.0.1:1234' vault
 ```
 
 ## Running Vault in Server Mode
 
 ```console
-$ docker run --cap-add=IPC_LOCK  -e 'VAULT_LOCAL_CONFIG={"backend": {"file": {"path": "/vault/file"}}, "default_lease_ttl": "168h", "max_lease_ttl": "720h"}' vault server
+$ docker run --cap-add=IPC_LOCK -e 'VAULT_LOCAL_CONFIG={"backend": {"file": {"path": "/vault/file"}}, "default_lease_ttl": "168h", "max_lease_ttl": "720h"}' vault server
 ```
 
 This runs a Vault server using the `file` storage backend at path `/vault/file`, with a default secret lease duration of one week and a maximum of 30 days.