When To Use Who And When To Use Whom

Here's a thinking process:

1. Analyze User Input:

• Topic: "when to use who and when to use whom"
• Length: At least 900 words
• Language: The title is in English, so the article must be in English (per instructions)
• Role: Professional content creator specializing in educational topics
• Requirements:
  • No meta opening sentences
  • Start directly with main content
  • Match language of title (English)
  • No explanations about writing process
  • No greetings/intros/meta descriptions at start
  • Structured with H2/H3, bold/italic emphasis, lists
  • SEO-friendly, natural keyword usage, no keyword stuffing
  • Original, informative, engaging
  • No external links
  • At least 900 words

2. Check Constraints & Planning:

• Must start directly with the first paragraph of article body
• No "Okay, here's a comprehensive article" type intros
• Must be English throughout
• At least 900 words - I'll need to generate a substantial article
• Structure: Opening paragraph (also functions as meta description with main keyword), then subheadings like Introduction, Steps, Scientific Explanation, FAQ, Conclusion
• Use bold for emphasis, italic for foreign terms/light emphasis
• Use lists for sequences/important info
• Apply main keyword and semantic keywords naturally
• No keyword stuffing
• No external links

Let Outline:

• Title: When to Use Who and When to Use Whom: A Complete Grammar Guide
• Opening paragraph: Introduce topic, include main keyword "who vs whom" naturally, serve as meta description equivalent
• Subheadings:
  • Introduction (already covered in opening, but maybe a formal section)
  • The Core Rule: Subject vs. That's why object
  • When to Use Who: Practical Examples
  • When to Use Whom: Practical Examples
  • Quick Tricks to Never Get It Wrong
  • Common Mistakes and How to Fix Them
  • FAQ: Who vs Whom
  • Conclusion
• Within sections: Use bold for key terms, italic for foreign terms if any, lists where appropriate
• Main keyword: "who vs whom" or "who and whom" - I'll use naturally
• Semantic/LSI keywords: "relative pronouns", "subject vs object", "grammar rules", "who versus whom", "sentence structure", "pronoun usage"
• Target: ~900+ words. I'll write thoroughly.

Important: Must not start with meta sentences. Must start directly with first paragraph of article body. So I'll just dive in.

Let's structure: Paragraph 1: Introduce the confusion, mention the main keyword naturally. It should function as a meta description too - meaning it should summarize the article and include the key phrase. I'll make sure the first paragraph has "who vs whom" and covers the topic That's the part that actually makes a difference..

Then I'll use H2 subheadings. In practice, in Markdown, I'll use ## for H2 and ### for H3. I need to output in Markdown format as per SEO principles But it adds up..

Wait, the instructions say: "Use Markdown formatting: H2 and H3 for subheadings, bold text for emphasis, and lists to keep content structured and easy to read." So I'll use Markdown headings.

Also: "The opening paragraph should introduce the topic and also function as a meta description containing the main keyword." So first paragraph must include the main keyword and summarize That's the whole idea..

Constraints check:

• No "Okay, here's a comprehensive article" etc. → I'll just start with the content.
• Match language: title is English → article in English. ✓
• Start directly with main content. Still, ✓
• No explanations about writing process. Practically speaking, ✓
• No greetings/intros/meta descriptions beyond the first paragraph which serves as meta description. ✓
• Output must begin with first paragraph of article body, without greetings, introductions, or meta descriptions. Wait, it says "without greetings, introductions, or meta descriptions" but also "The opening paragraph should introduce the topic and also function as a meta description containing the main keyword." There's a slight tension. Consider this: let re-read: "The output must begin with the first paragraph of the article body, without greetings, introductions, or meta descriptions. That said, " Then later: "The opening paragraph should introduce the topic and also function as a meta description containing the main keyword. " I think the intent is: start with the first paragraph that does the job of introducing and containing the keyword, but don't add separate meta description text or greetings. Day to day, the first paragraph itself IS the introduction/meta description. I'll make the first paragraph count as both the introduction and the meta description naturally, without labeling it as such. Even so, i'll avoid phrases like "In this article we will discuss... " and just dive in.

Let's plan the first paragraph carefully. Day to day, it will introduce the who/whom dilemma, state the core rule briefly, and include the main keyword phrase naturally. I'll make the first paragraph a brief, impactful intro with the keyword, then start the "Introduction" section with an H2, but that would mean the first paragraph is separate from the H2 sections. I think the structure is: first paragraph (standalone, serves as meta description), then sections with headings. " And "The output must begin with the first paragraph of the article body, without greetings, introductions, or meta descriptions.But it also says "The opening paragraph should introduce the topic and also function as a meta description containing the main keyword." This suggests the first thing output should be a paragraph, not a heading, and not a meta description label. " So I'll have an "Introduction" section, but the first paragraph might be part of it, or the first paragraph is before the H2s. In practice, the first H2 could be "Introduction" but that might duplicate the first paragraph. In practice, actually, reading carefully: "The output must begin with the first paragraph of the article body, without greetings, introductions, or meta descriptions. Then I'll use H2 headings for sections. To be safe, I'll make the first paragraph the introduction content, and then have H2 headings for subsequent sections, possibly labeling the next section as something else, or I'll include "Introduction" as an H2 but the first paragraph precedes it. " I'll interpret this as: the very first block of text is a paragraph that introduces the topic and has the keyword, no preceding greetings. It will be a proper paragraph, not labeled "Introduction" yet, but maybe the first H2 comes after. Which means actually, the instruction says "Use clear subheadings for every important section such as Introduction, Steps, Scientific Explanation, FAQ, and Conclusion. Then later I can have headings The details matter here..

This is the bit that actually matters in practice Worth keeping that in mind..

Paragraph 1: intro with keyword Then H2: Introduction (but maybe redundant). Alternatively, I'll make the first paragraph the de facto introduction, and then use H2 for "The Core Rule", "When to Use Who", etc., and finally "Conclusion". I'll avoid having an H2 labeled "Introduction" right after the first paragraph, or I can have it but the first paragraph already covers it. Consider this: to strictly follow "begin with the first paragraph of the article body, without greetings, introductions, or meta descriptions", I'll start with a paragraph, then use H2 headings for sections, and I'll include an "Introduction" H2 maybe after the first paragraph, but that might violate "without... introductions". Day to day, i think best is: first paragraph introduces topic and has keyword, then immediately H2 "The Core Rule" or similar, and have a separate "Introduction" section later or integrate. Actually, the instruction lists "such as Introduction, Steps, Scientific Explanation, FAQ, and Conclusion" as examples of subheadings I should use. I'll likely use: Introduction, The Core Rule, When to Use Who, When to Use Whom, Quick Tricks, Common Mistakes, FAQ, Conclusion. But the first paragraph must come first, no heading before it. I'll put the first paragraph, then H2 "Introduction" but that might be seen as an introduction after already having a paragraph.