Change deploy-tool to deploy-prototype

Author: Ayres, Andrew

episodes/02-Copy-Template.md

@@ -250,7 +250,7 @@ After the manual changes we made in the previous step, your tool XML will be cor
 To deploy your tool to the NDIP platform, you need to add the XML file to the galaxy-tools repository. The template includes a utility for this:
 
 ```bash
-poetry run deploy-tool
+poetry run deploy-prototype
 ```
 
 This script will:
@@ -282,11 +282,11 @@ Let's understand the key components that make your tool work in NDIP:
 
 3. **Deployment Process**:
    - When you push code to your repository → CI builds a new container
-   - When you run `deploy-tool` → The utility checks if your container exists and pushes your tool XML to the galaxy-tools prototype branch
+   - When you run `deploy-prototype` → The utility checks if your container exists and pushes your tool XML to the galaxy-tools prototype branch
    - After XML is merged → Your tool appears in the NDIP interface
 
 ::::::::::::::::::::::::::::::::::::::::: callout
-In a production environment, when your tool is ready for users, you would create a merge request from the prototype branch to the dev branch. The NDIP team reviews these changes, merges them, and your tool will be deployed to the production instance during the next deployment.
+In a production environment, when your tool is ready for users, you would run the deploy-production tool. This will create a merge request to the dev branch. The NDIP team reviews these changes, merges them, and your tool will be deployed to the production instance during the next deployment.
 ::::::::::::::::::::::::::::::::::::::::::::::::
 
 ## References

episodes/04-MVVM-Design-Pattern.md

@@ -360,7 +360,7 @@ Here are the steps to push your changes and deploy the tool:
 3. **Commit your changes:** Create a commit with a descriptive message: `git commit -m "Update Fractal tool with MVVM, bump to version 0.2.0"`.
 4. **Push to the repository:** Push your committed changes to the remote repository with `git push`.
 5. **Wait for CI/CD:** The push will trigger a CI/CD pipeline in gitlab. Wait for the pipeline to complete which includes building the container image for your tool. You can monitor the pipeline status in the Gitlab interface.
-6. **Deploy the tool:** Once the pipeline is successful, run the deployment command from your project's root directory: `poetry run deploy-tool`.
+6. **Deploy the tool:** Once the pipeline is successful, run the deployment command from your project's root directory: `poetry run deploy-prototype`.
 
 This process ensures that your updated tool is built, containerized, and made available through NDIP.