fix: standardize PR workflow wording between docs and code

- Standardize 'PRs' vs 'pull requests' terminology
- Standardize 'Ask user' vs 'Ask User' capitalization
- Ensure exact wording match: 'I can also apply PR workflow template'
- All 3 workflows now have identical PR workflow suggestions:
  * create_feature_workflow (feature implementation)
  * bug_triage_workflow (bug fixes)
  * implement_feature_workflow (implementation tasks)

Ensures documentation perfectly matches Kotlin implementation.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: jpicklyk

docs/workflow-prompts.md

@@ -714,7 +714,7 @@ This workflow provides intelligent feature implementation guidance with automati
 3. **Apply Appropriate Templates with Smart Detection**
    - **Always apply**: "Task Implementation Workflow" template for implementation tasks
    - **If git detected**: Automatically apply "Local Git Branching Workflow" template  
-   - **Ask user**: "Do you use GitHub/GitLab pull requests? If yes, I can apply PR workflow template"
+   - **Ask user**: "Do you use GitHub/GitLab PRs? If yes, I can also apply PR workflow template"
    - **If GitHub MCP available**: Mention GitHub MCP tools can automate PR creation and management
    - **For complex tasks**: Consider "Technical Approach" template for architectural guidance
 

src/main/kotlin/io/github/jpicklyk/mcptask/interfaces/mcp/WorkflowPromptsGuidance.kt

@@ -936,7 +936,7 @@ object WorkflowPromptsGuidance {
 
                             **If Git Detected**: Automatically apply "Local Git Branching Workflow" template
 
-                            **Ask User**: "Do you use GitHub/GitLab pull requests? If yes, I can apply PR workflow template"
+                            **Ask user**: "Do you use GitHub/GitLab PRs? If yes, I can also apply PR workflow template"
 
                             **If GitHub MCP Available**: Mention GitHub MCP tools can automate PR creation and management