Change "mount" to "secrets enable" in docs

website/source/docs/secrets/databases/mssql.html.md

@@ -86,7 +86,7 @@ of the role:
 
 Here is a complete example using Azure SQL Database. Note that databases in Azure SQL Database are [contained databases](https://docs.microsoft.com/en-us/sql/relational-databases/databases/contained-databases) and that we do not create a login for the user; instead, we associate the password directly with the user itself. Also note that you will need a separate connection and role for each Azure SQL database for which you want to generate dynamic credentials. You can use a single database backend mount for all these databases or use a separate mount for of them. In this example, we use a custom path for the database backend.
 
-First, we mount a database backend at the azuresql path with `vault mount -path=azuresql database`. Then we configure a connection called "testvault" to connect to a database called "test-vault", using "azuresql" at the beginning of our path:
+First, we mount a database backend at the azuresql path with `vault secrets enable -path=azuresql database`. Then we configure a connection called "testvault" to connect to a database called "test-vault", using "azuresql" at the beginning of our path:
 
 ```
 $ vault write azuresql/config/testvault \

website/source/docs/secrets/nomad/index.html.md

@@ -25,7 +25,7 @@ The first step to using the vault backend is to mount it.
 Unlike the `generic` backend, the `nomad` backend is not mounted by default.
 
 ```
-$ vault mount nomad
+$ vault secrets enable nomad
 Successfully mounted 'nomad' at 'nomad'!
 ```
 

website/source/docs/secrets/pki/index.html.md

@@ -222,7 +222,7 @@ The first step to using the PKI backend is to mount it. Unlike the `kv`
 backend, the `pki` backend is not mounted by default.
 
 ```text
-$ vault mount pki
+$ vault secrets enable pki
 Successfully mounted 'pki' at 'pki'!
 ```
 
@@ -435,7 +435,7 @@ To add another certificate authority to our Vault instance, we have to mount it
 at a different path.
 
 ```text
-$ vault mount -path=pki_int pki
+$ vault secrets enable -path=pki_int pki
 Successfully mounted 'pki' at 'pki_int'!
 ```
 

website/source/docs/secrets/ssh/dynamic-ssh-keys.html.md

@@ -78,7 +78,7 @@ First, however, the shared secret key must be specified.
 ### Mount the secrets engine
 
 ```text
-$ vault mount ssh
+$ vault secrets enable ssh
 Successfully mounted 'ssh' at 'ssh'!
 ```
 

website/source/docs/secrets/ssh/one-time-ssh-passwords.html.md

@@ -42,7 +42,7 @@ this secrets engine may allow for extra security on top of what TLS provides.
 ### Mount the secrets engine
 
 ```text
-$ vault mount ssh
+$ vault secrets enable ssh
 Successfully mounted 'ssh' at 'ssh'!
 ```
 

website/source/docs/secrets/ssh/signed-ssh-certificates.html.md

@@ -39,7 +39,7 @@ team, or configuration management tooling.
 must be mounted before use.
 
     ```text
-    $ vault mount -path=ssh-client-signer ssh
+    $ vault secrets enable -path=ssh-client-signer ssh
     Successfully mounted 'ssh' at 'ssh-client-signer'!
     ```
 
@@ -201,7 +201,7 @@ accidentally SSHing into an unmanaged or malicious machine.
 client signer.
 
     ```text
-    $ vault mount -path=ssh-host-signer ssh
+    $ vault secrets enable -path=ssh-host-signer ssh
     Successfully mounted 'ssh' at 'ssh-host-signer'!
     ```