Start updating docs

docs/cli/commands/export.mdx

@@ -39,6 +39,7 @@ Export environment variables from the platform into a file format.
 ```
 
 ### Environment variables
+
   <Accordion title="INFISICAL_TOKEN">
     Used to fetch secrets via a [machine identities](/documentation/platform/identities/machine-identities) apposed to logged in credentials. Simply, export this variable in the terminal before running this command.
 
@@ -47,13 +48,15 @@ Export environment variables from the platform into a file format.
     export INFISICAL_TOKEN=$(infisical login --method=universal-auth --client-id=<identity-client-id> --client-secret=<identity-client-secret> --silent --plain) # --plain flag will output only the token, so it can be fed to an environment variable. --silent will disable any update messages.
     ```
 
-
   <Info>
-    Alternatively you may also use service tokens. **Service tokens are legacy tokens that are a precursor to machine identities, and will be removed in the future.**
+    Alternatively, you may use service tokens.
+
+    Please note, however, that service tokens are being deprecated. They will be removed in the future in accordance with the deprecation notice and timeline stated [here](https://infisical.com/blog/deprecating-api-keys).
     ```bash
     # Example
     export INFISICAL_TOKEN=<service-token>
     ```
+
   </Info>
   </Accordion>
 
@@ -66,9 +69,11 @@ Export environment variables from the platform into a file format.
     # Example
     export INFISICAL_DISABLE_UPDATE_CHECK=true
     ```
+
   </Accordion>
 
 ### flags
+
   <Accordion title="--template">
     The `--template` flag specifies the path to the template file used for rendering secrets. When using templates, you can omit the other format flags.
 
@@ -88,6 +93,7 @@ Export environment variables from the platform into a file format.
     # Example
     infisical export --template="/path/to/template/file"
     ```
+
   </Accordion>
   <Accordion title="--env">
     Used to set the environment that secrets are pulled from.
@@ -100,6 +106,7 @@ Export environment variables from the platform into a file format.
     Note: this flag only accepts environment slug names not the fully qualified name. To view the slug name of an environment, visit the project settings page.
 
     default value: `dev`
+
   </Accordion>
 
   <Accordion title="--projectId">
@@ -111,24 +118,28 @@ Export environment variables from the platform into a file format.
 
     infisical export --projectId=XXXXXXXXXXXXXX
     ```
+
   </Accordion>
 
   <Accordion title="--expand">
     Parse shell parameter expansions in your secrets (e.g., `${DOMAIN}`)
 
     Default value: `true`
+
   </Accordion>
 
   <Accordion title="--format">
     Format of the output file. Accepted values: `dotenv`, `dotenv-export`, `csv`, `json` and `yaml`
 
     Default value: `dotenv`
+
   </Accordion>
 
   <Accordion title="--secret-overriding">
     Prioritizes personal secrets with the same name over shared secrets
 
     Default value: `true`
+
   </Accordion>
 
   <Accordion title="--path">
@@ -138,6 +149,7 @@ Export environment variables from the platform into a file format.
     # Example
     infisical export --path="/path/to/folder" --env=dev
     ```
+
   </Accordion>
 
   <Accordion title="--tags">
@@ -151,6 +163,7 @@ Export environment variables from the platform into a file format.
     Note: you must reference the tag by its slug name not its fully qualified name. Go to project settings to view all tag slugs.
 
     By default, all secrets are fetched
+
   </Accordion>
 
 </Accordion>

docs/cli/commands/run.mdx

@@ -11,6 +11,7 @@ description: "The command that injects your secrets into local environment"
     # Example
     infisical run [options] -- npm run dev
     ```
+
   </Tab>
 
   <Tab title="Chained commands">
@@ -20,6 +21,7 @@ description: "The command that injects your secrets into local environment"
     # Example
     infisical run [options] --command "npm run bootstrap && npm run dev start; other-bash-command"
     ```
+
   </Tab>
 </Tabs>
 
@@ -27,7 +29,6 @@ description: "The command that injects your secrets into local environment"
 
 Inject secrets from Infisical into your application process.
 
-
 ## Subcommands & flags
 
 <Accordion title="infisical run" defaultOpen="true">
@@ -41,6 +42,7 @@ Inject secrets from Infisical into your application process.
 ```
 
 ### Environment variables
+
   <Accordion title="INFISICAL_TOKEN">
     Used to fetch secrets via a [machine identity](/documentation/platform/identities/machine-identities) apposed to logged in credentials. Simply, export this variable in the terminal before running this command.
 
@@ -50,11 +52,14 @@ Inject secrets from Infisical into your application process.
     ```
 
     <Info>
-      Alternatively you may also use service tokens. **Service tokens are legacy tokens that are a precursor to machine identities, and will be removed in the future.**
+      Alternatively, you may use service tokens.
+
+      Please note, however, that service tokens are being deprecated. They will be removed in the future in accordance with the deprecation notice and timeline stated [here](https://infisical.com/blog/deprecating-api-keys).
       ```bash
       # Example
       export INFISICAL_TOKEN=<service-token>
       ```
+
   </Info>
   </Accordion>
 
@@ -67,6 +72,7 @@ Inject secrets from Infisical into your application process.
     # Example
     export INFISICAL_DISABLE_UPDATE_CHECK=true
     ```
+
   </Accordion>
 
 ### Flags
@@ -78,6 +84,7 @@ Inject secrets from Infisical into your application process.
     # Example
     infisical run --project-config-dir=/some-dir -- printenv
     ```
+
   </Accordion>
 
   <Accordion title="--command">
@@ -87,6 +94,7 @@ Inject secrets from Infisical into your application process.
     # Example
     infisical run --command="npm run build && npm run dev; more-commands..."
     ```
+
   </Accordion>
 
   <Accordion title="--projectId">
@@ -96,6 +104,7 @@ Inject secrets from Infisical into your application process.
     # Example
     infisical run --projectId=<project-id> -- npm run dev
     ```
+
   </Accordion>
 
   <Accordion title="--token">
@@ -107,24 +116,29 @@ Inject secrets from Infisical into your application process.
     ```
 
     You may also expose the token to the CLI by setting the environment variable `INFISICAL_TOKEN` before executing the run command. This will have the same effect as setting the token with `--token` flag
+
   </Accordion>
 
   <Accordion title="--expand">
     Turn on or off the shell parameter expansion in your secrets. If you have used shell parameters in your secret(s), activating this feature will populate them before injecting them into your application process.
 
     Default value: `true`
+
   </Accordion>
 
-  <Accordion title="--env">
+{" "}
-    This is used to specify the environment from which secrets should be retrieved. The accepted values are the environment slugs defined for your project, such as `dev`, `staging`, `test`, and `prod`.
 
-    Default value: `dev`
+<Accordion title="--env">
+  This is used to specify the environment from which secrets should be
+  retrieved. The accepted values are the environment slugs defined for your
+  project, such as `dev`, `staging`, `test`, and `prod`. Default value: `dev`
 </Accordion>
 
   <Accordion title="--secret-overriding">
     Prioritizes personal secrets with the same name over shared secrets
 
     Default value: `true`
+
   </Accordion>
 
   <Accordion title="--tags">
@@ -138,6 +152,7 @@ Inject secrets from Infisical into your application process.
     Note: you must reference the tag by its slug name not its fully qualified name. Go to project settings to view all tag slugs.
 
     By default, all secrets are fetched
+
   </Accordion>
 
   <Accordion title="--path">

docs/cli/commands/secrets.mdx

@@ -31,12 +31,15 @@ $ infisical secrets
     ```
 
     <Info>
-      Alternatively you may also use service tokens. **Service tokens are legacy tokens that are a precursor to machine identities, and will be removed in the future.**
+      Alternatively, you may use service tokens.
+
+      Please note, however, that service tokens are being deprecated. They will be removed in the future in accordance with the deprecation notice and timeline stated [here](https://infisical.com/blog/deprecating-api-keys).
       ```bash
       # Example
       export INFISICAL_TOKEN=<service-token>
       ```
     </Info>
+
   </Accordion>
 
   <Accordion title="INFISICAL_DISABLE_UPDATE_CHECK">
@@ -67,6 +70,7 @@ $ infisical secrets
     # Example
     infisical secrets --projectId=<project-id>
     ```
+
   </Accordion>
 
   <Accordion title="--env">
@@ -202,7 +206,7 @@ $ infisical secrets folders
     </Accordion>
 
     <Accordion title="--token">
-      Fetch folders using an Infisical universal auth access token
+      Fetch folders using an [machine identity](/documentation/platform/identities/machine-identities) access token.
 
       Default value: ``
     </Accordion>