docs: Improve instructions for sentence cases (#2247)

<!-- CURSOR_SUMMARY -->
> [!NOTE]
> **Low Risk**
> Documentation-only changes that adjust guidance/checklists without
affecting product code or runtime behavior.
> 
> **Overview**
> Clarifies sentence-case heading guidance by adding an expanded
**"Common mistakes"** table (proper nouns, acronyms, and capitalization
after colons) to `content-standards.md` and reinforcing the same rules
in `writing-style.md`, including additional no-gerund heading examples.
> 
> Adds a new `quality-standards.md` section requiring line-by-line
verification of any regex/find-and-replace or other automated mass edits
before committing, highlighting common breakage areas (headings, code,
links, and terminology).
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
aa12068. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>

Author: marcel-rbro

.claude/rules/content-standards.md

@@ -62,10 +62,28 @@ slug: /academy/tutorials/web-scraper
 
 **Sentence case only.** Capitalize only the first word and proper nouns.
 
-| Avoid | Prefer |
-|-------|--------|
-| Store And Manage Data | Store and manage data |
-| Getting Started With Actors | Get started with Actors |
+#### Common mistakes
+
+| Avoid (Title Case) | Prefer (Sentence case) | Rule |
+|-------------------|------------------------|------|
+| Store And Manage Data | Store and manage data | Lowercase articles, conjunctions, prepositions |
+| Getting Started With Actors | Get started with Actors | "Actors" stays capitalized (Apify product name) |
+| Use The Apify SDK | Use the Apify SDK | "SDK" stays capitalized (acronym) |
+| Advanced Web Scraping Techniques | Advanced web scraping techniques | Lowercase generic terms |
+| Configure GitHub Actions | Configure GitHub Actions | Preserve proper noun capitalization |
+| Connect To Google Sheets | Connect to Google Sheets | Lowercase prepositions ("to") |
+| Set Up Your Environment | Set up your environment | Lowercase articles ("your") |
+| API Reference Documentation | API reference documentation | Keep acronyms capitalized, rest lowercase |
+| Working With Docker Containers | Work with Docker containers | "Docker" stays capitalized (product name) |
+| Extend The Base Image | Extend the base image | Lowercase "the" mid-sentence |
+| How Do I Start? | How do I start? | Capitalize "I" in questions |
+| Understanding Request Queues | Understand request queues | Lowercase feature names |
+| Enable Standby Mode | Enable standby mode | Lowercase mode names |
+| Access The Apify Console | Access the Apify Console | "Apify Console" stays capitalized (product) |
+| Run Your First Actor | Run your first Actor | "Actor" capitalized, "your" lowercase |
+| Manage Node Modules | Manage node modules | Lowercase generic terms |
+| Step 1: install the dependencies | Step 1: Install the dependencies | Capitalize after colon (starts new clause) |
+| Option 2: use the alternative approach | Option 2: Use the alternative approach | Capitalize after colon (starts new clause) |
 
 ### Form
 

.claude/rules/quality-standards.md

@@ -8,6 +8,30 @@ alwaysApply: true
 
 Comprehensive quality checklist for all Apify documentation. Use this before submitting any content for review.
 
+## Automated changes verification
+
+:::danger Critical requirement for AI assistants
+
+**When using regex, find-and-replace, or any automated command to perform mass changes across files, you MUST verify every single change individually before committing.**
+
+Automated replacements are error-prone and can break:
+- **Headings:** Proper nouns (GitHub, Docker), Apify products (Actors, Console), acronyms (API, SDK), capitalization after colons
+- **Code examples:** Variable names, API endpoints, function calls, configuration values
+- **Links:** URL paths, anchor references, file paths
+- **Terminology:** Product names, feature names, technical terms with specific capitalization
+- **Context-specific formatting:** Bold UI elements vs regular text, inline code vs prose
+
+**Required process:**
+1. Run the automated replacement command
+1. Review the complete `git diff` output
+1. Check every single changed line individually
+1. Manually correct any broken proper nouns, acronyms, or context-dependent cases
+1. Only commit after verifying all changes line-by-line
+
+Never commit automated changes without verifying each one. Use diff tools to catch errors before committing.
+
+:::
+
 ## Complete quality checklist
 
 Before submitting documentation, verify:

.claude/rules/writing-style.md

@@ -76,9 +76,24 @@ Use active voice. Avoid gendered terms. Don't use directional language ("left/ri
 
 **Sentence case only.** No title case.
 
-| Avoid                 | Prefer                |
-| --------------------- | --------------------- |
+Common mistakes: Capitalizing articles (the, a, an), prepositions (to, with, from), and conjunctions (and, or, but).
+
+| Avoid (Title Case) | Prefer (Sentence case) |
+| ------------------ | ---------------------- |
 | Store And Manage Data | Store and manage data |
+| Use The Apify SDK | Use the Apify SDK |
+| Connect To Google Sheets | Connect to Google Sheets |
+| Configure GitHub Actions | Configure GitHub Actions |
+| How Do I Start? | How do I start? |
+
+**Preserve proper nouns and acronyms:** Apify products (Actors, Console, Proxy), external tools (GitHub, Docker, Playwright), and acronyms (API, SDK, CLI) stay capitalized.
+
+**Capitalize after colons:** When a colon introduces a complete clause or instruction, capitalize the first word after it.
+
+| Avoid | Prefer |
+| ----- | ------ |
+| Step 1: install the dependencies | Step 1: Install the dependencies |
+| Option 2: use the alternative | Option 2: Use the alternative |
 
 **No gerunds (-ing forms).** Use noun phrases or imperatives.
 
@@ -87,6 +102,11 @@ Use active voice. Avoid gendered terms. Don't use directional language ("left/ri
 | Finding available tags        | Available tags             |
 | Getting started with Actors   | Get started with Actors    |
 | Understanding the API         | API overview               |
+| Setting up your environment   | Set up your environment    |
+| Using Docker containers       | Use Docker containers      |
+| Building your first Actor     | Build your first Actor     |
+| Running the scraper           | Run the scraper            |
+| Extending the base image      | Extend the base image      |
 
 Rationale: Noun-phrase headings are more scannable and search-friendly (Microsoft style guide).