lowercase g in goose (#4832)

.github/ISSUE_TEMPLATE/config.yml

@@ -1,6 +1,6 @@
 blank_issues_enabled: false
 contact_links:
-  - name: Goose Discord discussion
+  - name: goose Discord discussion
     url: https://discord.gg/block-opensource
     about: Please ask and answer questions here.
   - name: Report a security vulnerability

.github/ISSUE_TEMPLATE/submit-recipe.yml

@@ -1,25 +1,25 @@
-name: 🧑‍🍳 Submit a Recipe to the Goose Cookbook
-description: Share a reusable Goose recipe with the community!
+name: 🧑‍🍳 Submit a recipe to the goose cookbook
+description: Share a reusable goose recipe with the community!
 title: "[Recipe] <your recipe title here>"
 labels: ["recipe submission"]
 body:
   - type: markdown
     attributes:
       value: |
-        Thanks for contributing to the Goose Cookbook! 🍳  
-        Recipes are reusable sessions created in Goose Desktop or CLI and shared with the community to help others vibe code faster.
+        Thanks for contributing to the goose cookbook! 🍳  
+        Recipes are reusable sessions created in goose desktop or CLI and shared with the community to help others vibe code faster.
 
         📌 **How to Submit**
-        - Create your recipe using Goose ("Make recipe from this session")
+        - Create your recipe using goose ("Make recipe from this session")
         - Fill out the YAML below using the format provided
-        - Paste it into the field and submit the issue — we'll review and add it to the Cookbook!
+        - Paste it into the field and submit the issue — we'll review and add it to the cookbook!
 
         🪄 **What Happens After?**
-        - If accepted, we'll publish your recipe to the [Goose Recipes Cookbook](https://block.github.io/goose/recipes)
+        - If accepted, we'll publish your recipe to the [goose recipes cookbook](https://block.github.io/goose/recipes)
         - You'll receive OpenRouter **LLM API credits** as a thank you!
         - Your GitHub handle will be displayed and linked on the recipe card
         - If you provide an email below, we'll email you your credits when your recipe is approved and merged.
-        - If the YAML has any issues, Goose will comment with validation errors so you can fix and resubmit.
+        - If the YAML has any issues, goose will comment with validation errors so you can fix and resubmit.
 
         🧪 **Pro Tip:** You can test your recipe locally in your terminal with:  
         `goose recipe validate your-recipe.yaml`
@@ -28,7 +28,7 @@ body:
     id: recipe-yaml
     attributes:
       label: Paste Your Full Recipe YAML Below
-      description: Use the structure below and we’ll auto-fill your GitHub handle for `author.contact` after submission.
+      description: Use the structure below and we'll auto-fill your GitHub handle for `author.contact` after submission.
       placeholder: |
         version: "1.0.0"
         id: clean-up-feature-flag
@@ -103,8 +103,8 @@ body:
         - `id` should be lowercase, hyphenated, and unique (e.g. `my-awesome-recipe`)
         - `title` is the display name of your recipe
         - `description` should clearly explain what the recipe does
-        - `instructions` are specific steps Goose should follow — supports template variables like `{{ variable_name }}`
-        - `prompt` is the first thing Goose sees when the recipe is launched
+        - `instructions` are specific steps goose should follow — supports template variables like `{{ variable_name }}`
+        - `prompt` is the first thing goose sees when the recipe is launched
         - `parameters` should include required or optional inputs — optional ones must have `default`
         - `extensions` must follow the full format with `type`, `cmd`, `args`, `timeout`, etc.
         - `activities` describe the main actions the recipe performs