docs: lowercase goose in remaining topics (#5861)

documentation/docs/tutorials/plan-feature-devcontainer-setup.md

@@ -1,6 +1,6 @@
 ---
 title: "Planning Complex Tasks"
-description: "Learn how to use Goose's Plan feature to break down complex tasks into manageable, executable steps."
+description: "Learn how to use goose's Plan feature to break down complex tasks into manageable, executable steps."
 ---
 
 # Planning Complex Tasks
@@ -8,15 +8,15 @@ description: "Learn how to use Goose's Plan feature to break down complex tasks
 *Transform overwhelming tasks into systematic, step-by-step execution plans*
 
 
-Using Goose for large, complex tasks can feel overwhelming, especially when you're unsure of exactly how you want to approach it in advance. I experienced this when I needed to set up a complex development environment for an [API course](https://github.com/LinkedInLearning/java-automated-api-testing-with-rest-assured-5989068) I published. Between Docker configurations, database initialization, devcontainer setup, and GitHub Codespaces integration, there are dozens of moving pieces that need to work together perfectly. One missing configuration or incorrect dependency can derail the entire process.
+Using goose for large, complex tasks can feel overwhelming, especially when you're unsure of exactly how you want to approach it in advance. I experienced this when I needed to set up a complex development environment for an [API course](https://github.com/LinkedInLearning/java-automated-api-testing-with-rest-assured-5989068) I published. Between Docker configurations, database initialization, devcontainer setup, and GitHub Codespaces integration, there are dozens of moving pieces that need to work together perfectly. One missing configuration or incorrect dependency can derail the entire process.
 
-This tutorial shows you how to use Goose's [Plan feature](/docs/guides/multi-model/creating-plans) to transform a complex devcontainer setup into a systematic, executable roadmap. You'll learn how to brainstorm with Goose, refine your requirements, and let Goose create both a detailed plan and implementation checklist.
+This tutorial shows you how to use goose's [Plan feature](/docs/guides/multi-model/creating-plans) to transform a complex devcontainer setup into a systematic, executable roadmap. You'll learn how to brainstorm with goose, refine your requirements, and let goose create both a detailed plan and implementation checklist.
 
 ## What You'll Learn
 
 By the end of this tutorial, you'll understand how to:
 
-- Use Goose's Plan feature to break down complex technical projects
+- Use goose's Plan feature to break down complex technical projects
 - Brainstorm and refine requirements through AI-assisted conversation
 - Transform high-level goals into detailed, executable steps
 - Create comprehensive checklists for validation and quality assurance
@@ -37,23 +37,23 @@ This involves coordinating multiple technologies: Docker, MySQL, PHP, Java, devc
 
 ## Step 1: Initial Brainstorming Session
 
-Let's start by having a brainstorming conversation with Goose to clarify our requirements.
+Let's start by having a brainstorming conversation with goose to clarify our requirements.
 
 :::info Planning in Desktop vs CLI
-The Goose Desktop doesn't have a `/plan` keyword like the CLI. In Desktop, you need to explicitly ask Goose to create a plan:
+The goose Desktop doesn't have a `/plan` keyword like the CLI. In Desktop, you need to explicitly ask goose to create a plan:
 
 ```
-"Hey Goose, can you create a plan to set up my GitHub repo for Codespaces with automatic Docker startup? Please don't start the actual work yet."
+"Hey goose, can you create a plan to set up my GitHub repo for Codespaces with automatic Docker startup? Please don't start the actual work yet."
 ```
 
-In the CLI, you can enter plan mode with `/plan` and Goose will ask clarifying questions before generating the plan. Unless you specifically ask Goose Desktop to "create a plan", it might jump straight into implementation.
+In the CLI, you can enter plan mode with `/plan` and goose will ask clarifying questions before generating the plan. Unless you specifically ask goose Desktop to "create a plan", it might jump straight into implementation.
 :::
 
 ### Starting the Conversation
 
 **You:** _"I need help setting up a GitHub repository for automated API testing. Students should be able to open it in GitHub Codespaces and immediately start writing tests without any manual setup. Can you help me think through what's needed?"_
 
-**Goose:** _"I'd be happy to help you design this automated setup! Let me ask some clarifying questions to understand your requirements better:_
+**goose:** _"I'd be happy to help you design this automated setup! Let me ask some clarifying questions to understand your requirements better:_
 
 1. What type of API are you working with? (REST, GraphQL, etc.)
 2. What testing framework do you want students to use?
@@ -65,7 +65,7 @@ In the CLI, you can enter plan mode with `/plan` and Goose will ask clarifying q
 
 **You:** _"It's a REST API built in PHP that students will test using Rest Assured in Java. They need a real MySQL database with actual test data so they can practice realistic scenarios. The API has endpoints for managing products and categories in an e-commerce system."_
 
-**Goose:** _"Perfect! That gives me a clear picture. A few more questions to ensure we design this correctly:_
+**goose:** _"Perfect! That gives me a clear picture. A few more questions to ensure we design this correctly:_
 
 1. Do you already have the PHP API code, or do we need to create it?
 2. What version of Java should the environment support?
@@ -77,7 +77,7 @@ In the CLI, you can enter plan mode with `/plan` and Goose will ask clarifying q
 
 ## Step 2: Creating the Detailed Plan
 
-Now that we've clarified the requirements, let's ask Goose to create a comprehensive plan.
+Now that we've clarified the requirements, let's ask goose to create a comprehensive plan.
 
 ### Requesting the Plan
 
@@ -85,7 +85,7 @@ Now that we've clarified the requirements, let's ask Goose to create a comprehen
 
 ### The Generated Plan
 
-Goose will generate a comprehensive plan similar to this:
+goose will generate a comprehensive plan similar to this:
 
 <details>
   <summary>GitHub Codespaces API Testing Environment Setup Plan</summary>
@@ -295,15 +295,15 @@ Create a GitHub repository that automatically provisions a complete development
 
 ## Step 3: Detailed Implementation Planning
 
-Now let's ask Goose to create the specific implementation prompt that will guide the execution.
+Now let's ask goose to create the specific implementation prompt that will guide the execution.
 
 ### Creating the Implementation Prompt
 
-**You:**  _"This plan looks comprehensive! Can you now create a detailed implementation prompt that I can use to execute this plan? I want something specific enough that Goose can follow it step-by-step without needing additional clarification."_
+**You:**  _"This plan looks comprehensive! Can you now create a detailed implementation prompt that I can use to execute this plan? I want something specific enough that goose can follow it step-by-step without needing additional clarification."_
 
 ### The Implementation Prompt
 
-Goose will generate a detailed prompt like this:
+goose will generate a detailed prompt like this:
 
 <details>
     <summary>Detailed Prompt</summary>
@@ -370,11 +370,11 @@ With our detailed plan and implementation prompt ready, we can now execute the s
 
 **You:** _"Perfect! Now let's implement this plan. Here's the detailed prompt we created: [paste the implementation prompt]"_
 
-Goose will now work through each step of the plan, creating the necessary files and configurations.
+goose will now work through each step of the plan, creating the necessary files and configurations.
 
 ### Monitoring Progress
 
-As Goose implements the plan, you can verify each deliverable against the checklist we created:
+As goose implements the plan, you can verify each deliverable against the checklist we created:
 
 1. **File Creation**: Check that each required file is created in the correct location
 2. **Configuration Accuracy**: Verify that configurations match the specifications
@@ -408,11 +408,11 @@ If issues arise during implementation or testing, use the plan as a reference to
 - **Permission Problems**: Update Dockerfile with proper permissions
 - **Configuration Errors**: Verify environment variables and connection strings
 
-## Best Practices for Planning with Goose
+## Best Practices for Planning with goose
 
 1. Start with brainstorming. Don't jump straight to asking for a plan. Have a conversation to clarify requirements and explore options.
 2. Be specific about deliverables. Ask for concrete deliverables, file names, and validation criteria for each step.
-3. Ask Goose to identify potential issues and provide mitigation strategies.
+3. Ask goose to identify potential issues and provide mitigation strategies.
 4. Generate detailed implementation prompts that can guide execution without additional clarification.
 5. Include specific ways to verify that each step worked correctly.
 
@@ -424,7 +424,7 @@ For very complex projects, break the plan into phases and tackle them incrementa
 **You:** _"This plan is quite comprehensive. Can you break it into smaller phases that I can implement and test independently?"_
 
 ### Dependency Mapping
-Ask Goose to identify dependencies between tasks:
+Ask goose to identify dependencies between tasks:
 
 **You:** _"Which of these tasks can be done in parallel, and which have dependencies on other tasks?"_
 
@@ -435,7 +435,7 @@ Explore different implementation strategies:
 
 ## Conclusion
 
-Goose's Plan feature transforms complex technical challenges from overwhelming problems into systematic, executable roadmaps. By following this tutorial's approach:
+goose's Plan feature transforms complex technical challenges from overwhelming problems into systematic, executable roadmaps. By following this tutorial's approach:
 
 1. **Brainstorm** to clarify requirements and explore options
 2. **Plan** to break down complexity into manageable steps
@@ -445,13 +445,13 @@ Goose's Plan feature transforms complex technical challenges from overwhelming p
 
 You can tackle any complex development environment setup with confidence, knowing that you have a clear path forward and specific criteria for success.
 
-The key is treating Goose as a planning partner, not just a code generator. Give it the full context of what you're trying to achieve, and let it help you think through the complexity before diving into implementation.
+The key is treating goose as a planning partner, not just a code generator. Give it the full context of what you're trying to achieve, and let it help you think through the complexity before diving into implementation.
 
 ## Next Steps
 
 - Try this approach with your own complex setup challenges
 - Experiment with different types of planning prompts
-- Share your planning successes with the [Goose community](https://discord.gg/goose-oss)
+- Share your planning successes with the [goose community](https://discord.gg/goose-oss)
 - Explore how planning integrates with [Lead/Worker mode](/docs/tutorials/lead-worker) or [Subagents](/docs/guides/subagents) for even more sophisticated workflows
 
 Remember, the goal is to get the right approach, in the right order, with the right safeguards. That's what makes the difference between a quick fix and a robust, maintainable solution.