Drop images from secrets

docs/platform/secrets.mdx

@@ -11,14 +11,10 @@ Secrets are encrypted at rest and stored in the database.
 
 Secrets are scoped to a workspace. To add a secret, navigate to the **Credentials** page and click on the **Create Secret** button.
 
-![Create secret](/img/platform/credentials/create-secret.png)
-
 ## Retrieving secrets in workflows
 
 To get a secret and use it in an action input, use the `SECRETS.<secret-name>.<secret-key>` syntax.
 
-![Retrieve secret](/img/platform/credentials/retrieve-secret.png)
-
 Tracecat will automatically replace the expression with the secret value at runtime.
 Retrieved secrets are deleted from memory after the workflow run completes.
 
@@ -31,8 +27,6 @@ Retrieved secrets are deleted from memory after the workflow run completes.
 Pre-built integrations require a specific secret name and required keys.
 For example, the VirusTotal integration requires a secret with the name `virustotal` and the key `VIRUSTOTAL_API_KEY`.
 
-![VirusTotal integration](/img/platform/credentials/virustotal-integration.png)
-
 Different integrations may require different required and optional keys.
 For example, Tracecat's AWS integration is configured with the following secret with optional keys:
 
@@ -60,8 +54,6 @@ Check out the [Quickstart](/tutorials/1-quickstart) tutorial for a step-by-step
 Tracecat also supports organization-level secrets that are accessible to all workspaces within an organization.
 To create an organization-level secret, navigate to the **Organization** page and click on the **Create Secret** button.
 
-![Create organization secret](/img/platform/credentials/create-organization-secret.png)
-
 ## Multi-tenant secrets
 
 A common use case is to have different sets of the same secret for different tenants or environments.