docs(contributing): use action verbs for all PR types including docs

docs/CONTRIBUTING.md

@@ -187,7 +187,7 @@
 ### Scoping
 
 > [!TIP]
 > Here's a [good resource](https://youtu.be/bmSAYlu0NcY?si=2lLQeY1PGCY9tcvX) on software design philosophy.
 
 When planning the scope of work, make sure you
 [keep PRs small](https://artsy.github.io/blog/2021/03/09/strategies-for-small-focused-pull-requests/).
@@ -231,6 +231,16 @@
    Correct: "Gracefully recover from connection errors"
 1. **Use user action verbs**: _View, Play, Customize, Save_, etc.
 
+> [!WARNING]
+> This rule applies to **all PR types**, including `docs`. Do not use verbs that
+> describe what you did ("document", "update", "add") — use verbs that describe
+> what users can now do.
+>
+> | **Good** ✅                                        | **Bad** ❌                                          |
+> | -------------------------------------------------- | --------------------------------------------------- |
+> | `docs(typefully): log in with shared account`      | `docs(typefully): document shared account`          |
+> | `docs(api): authenticate with OAuth`               | `docs(api): add OAuth section to README`            |
+
 #### Before Submitting, Ask
 
 1. Does it use `type(scope [Optional]): action` format?
@@ -240,7 +250,7 @@
 
 #### Design PRs
 
 Design PRs use `docs(ui)` as the type and scope. e.g.: `docs(ui): design table component`
 
 Initiate a PR with a note in the DESIGN.md file detailing the addressed design
 aspects. Structure the design file with the following markup:
@@ -272,7 +282,7 @@
       - [[Bid Popup]](https://figma.com/your-design-file-url)
 ```
 
 If there isn't an existing DESIGN.md file, create one and link it from README.md.
 
 ### PR Lifecycle