adjust aop to amp docs lang (#4179)

* adjust aop to amp docs lang

* whoop no print

docs/en/enterprise/guides/deploy-crew.mdx

@@ -1,22 +1,26 @@
 ---
 title: "Deploy Crew"
-description: "Deploying a Crew on CrewAI AOP"
+description: "Deploying a Crew on CrewAI AMP"
 icon: "rocket"
 mode: "wide"
 ---
 
 <Note>
-After creating a crew locally or through Crew Studio, the next step is deploying it to the CrewAI AOP platform. This guide covers multiple deployment methods to help you choose the best approach for your workflow.
+  After creating a crew locally or through Crew Studio, the next step is
+  deploying it to the CrewAI AMP platform. This guide covers multiple deployment
+  methods to help you choose the best approach for your workflow.
 </Note>
 
 ## Prerequisites
 
 <CardGroup cols={2}>
   <Card title="Crew Ready for Deployment" icon="users">
-    You should have a working crew either built locally or created through Crew Studio
+    You should have a working crew either built locally or created through Crew
+    Studio
   </Card>
   <Card title="GitHub Repository" icon="github">
-    Your crew code should be in a GitHub repository (for GitHub integration method)
+    Your crew code should be in a GitHub repository (for GitHub integration
+    method)
   </Card>
 </CardGroup>
 
@@ -39,10 +43,10 @@ The CLI provides the fastest way to deploy locally developed crews to the Enterp
   </Step>
 
   <Step title="Authenticate with the Enterprise Platform">
-    First, you need to authenticate your CLI with the CrewAI AOP platform:
+    First, you need to authenticate your CLI with the CrewAI AMP platform:
 
     ```bash
-    # If you already have a CrewAI AOP account, or want to create one:
+    # If you already have a CrewAI AMP account, or want to create one:
     crewai login
     ```
 
@@ -105,38 +109,38 @@ The CLI provides the fastest way to deploy locally developed crews to the Enterp
 
 The CrewAI CLI offers several commands to manage your deployments:
 
-  ```bash
-  # List all your deployments
-  crewai deploy list
+```bash
+# List all your deployments
+crewai deploy list
 
-  # Get the status of your deployment
-  crewai deploy status
+# Get the status of your deployment
+crewai deploy status
 
-  # View the logs of your deployment
-  crewai deploy logs
+# View the logs of your deployment
+crewai deploy logs
 
-  # Push updates after code changes
-  crewai deploy push
+# Push updates after code changes
+crewai deploy push
 
-  # Remove a deployment
-  crewai deploy remove <deployment_id>
-  ```
+# Remove a deployment
+crewai deploy remove <deployment_id>
+```
 
 ## Option 2: Deploy Directly via Web Interface
 
-You can also deploy your crews directly through the CrewAI AOP web interface by connecting your GitHub account. This approach doesn't require using the CLI on your local machine.
+You can also deploy your crews directly through the CrewAI AMP web interface by connecting your GitHub account. This approach doesn't require using the CLI on your local machine.
 
 <Steps>
 
   <Step title="Pushing to GitHub">
 
-  You need to push your crew to a GitHub repository. If you haven't created a crew yet, you can [follow this tutorial](/en/quickstart).
+You need to push your crew to a GitHub repository. If you haven't created a crew yet, you can [follow this tutorial](/en/quickstart).
 
   </Step>
 
-  <Step title="Connecting GitHub to CrewAI AOP">
+  <Step title="Connecting GitHub to CrewAI AMP">
 
-    1. Log in to [CrewAI AOP](https://app.crewai.com)
+    1. Log in to [CrewAI AMP](https://app.crewai.com)
     2. Click on the button "Connect GitHub"
 
     <Frame>
@@ -194,7 +198,7 @@ For automated deployments in CI/CD pipelines, you can use the CrewAI API to trig
 <Steps>
   <Step title="Get Your Personal Access Token">
 
-    Navigate to your CrewAI AOP account settings to generate an API token:
+    Navigate to your CrewAI AMP account settings to generate an API token:
 
     1. Go to [app.crewai.com](https://app.crewai.com)
     2. Click on **Settings** → **Account** → **Personal Access Token**
@@ -207,7 +211,7 @@ For automated deployments in CI/CD pipelines, you can use the CrewAI API to trig
 
     Locate the unique identifier for your deployed crew:
 
-    1. Go to **Automations** in your CrewAI AOP dashboard
+    1. Go to **Automations** in your CrewAI AMP dashboard
     2. Select your existing automation/crew
     3. Click on **Additional Details**
     4. Copy the **UUID** - this identifies your specific crew deployment
@@ -238,7 +242,6 @@ For automated deployments in CI/CD pipelines, you can use the CrewAI API to trig
     If your automation was first created connected to Git, the API will automatically pull the latest changes from your repository before redeploying.
     </Info>
 
-
   </Step>
 
   <Step title="GitHub Actions Integration Example">
@@ -276,12 +279,14 @@ For automated deployments in CI/CD pipelines, you can use the CrewAI API to trig
     </Tip>
 
     </Step>
+
   </Steps>
 
 ## ⚠️ Environment Variable Security Requirements
 
 <Warning>
-**Important**: CrewAI AOP has security restrictions on environment variable names that can cause deployment failures if not followed.
+  **Important**: CrewAI AMP has security restrictions on environment variable
+  names that can cause deployment failures if not followed.
 </Warning>
 
 ### Blocked Environment Variable Patterns
@@ -289,12 +294,14 @@ For automated deployments in CI/CD pipelines, you can use the CrewAI API to trig
 For security reasons, the following environment variable naming patterns are **automatically filtered** and will cause deployment issues:
 
 **Blocked Patterns:**
+
 - Variables ending with `_TOKEN` (e.g., `MY_API_TOKEN`)
 - Variables ending with `_PASSWORD` (e.g., `DB_PASSWORD`)
 - Variables ending with `_SECRET` (e.g., `API_SECRET`)
 - Variables ending with `_KEY` in certain contexts
 
 **Specific Blocked Variables:**
+
 - `GITHUB_USER`, `GITHUB_TOKEN`
 - `AWS_REGION`, `AWS_DEFAULT_REGION`
 - Various internal CrewAI system variables
@@ -302,6 +309,7 @@ For security reasons, the following environment variable naming patterns are **a
 ### Allowed Exceptions
 
 Some variables are explicitly allowed despite matching blocked patterns:
+
 - `AZURE_AD_TOKEN`
 - `AZURE_OPENAI_AD_TOKEN`
 - `ENTERPRISE_ACTION_TOKEN`
@@ -331,7 +339,8 @@ API_CONFIG=secret123
 4. **Document changes**: Keep track of renamed variables for your team
 
 <Tip>
-If you encounter deployment failures with cryptic environment variable errors, check your variable names against these patterns first.
+  If you encounter deployment failures with cryptic environment variable errors,
+  check your variable names against these patterns first.
 </Tip>
 
 ### Interact with Your Deployed Crew
@@ -339,6 +348,7 @@ If you encounter deployment failures with cryptic environment variable errors, c
 Once deployment is complete, you can access your crew through:
 
 1. **REST API**: The platform generates a unique HTTPS endpoint with these key routes:
+
    - `/inputs`: Lists the required input parameters
    - `/kickoff`: Initiates an execution with provided inputs
    - `/status/{kickoff_id}`: Checks the execution status
@@ -378,5 +388,6 @@ The Enterprise platform also offers:
 - **Crew Studio**: Build crews through a chat interface without writing code
 
 <Card title="Need Help?" icon="headset" href="mailto:support@crewai.com">
-  Contact our support team for assistance with deployment issues or questions about the Enterprise platform.
+  Contact our support team for assistance with deployment issues or questions
+  about the Enterprise platform.
 </Card>