Keep One Name for Each Thing in Your Blog Post

Prefer one stable name for each object in a task-focused blog post, and give different objects different names. If a reader needs to choose between documents, changing their names for variety asks the reader to infer which document you mean. I would spend that variety on the surrounding explanation instead.

Under its additional machine-translation advice, Microsoft's writing guide recommends consistent naming for a concept and advises against using the same term for different concepts or features. The retained page, checked on 8 October 2026, gives June 14, 2023 as its last update. That recommendation comes from a localization context; the edit below applies its naming principle to a fictional blog passage, without claiming a translation or reader-test result.

Decide what each name refers to

Here are the complete supplied definitions for an invented walking-guide exercise. All documents, the outside note and the passage are original teaching material; no real trip or recorded visits are reported.

• Route card: lists the planned stop codes in order.

• Stop list: pairs each stop code with its stop name.

• Trip log: records the codes actually visited.

These documents have different jobs. The route card specifies a planned sequence. The stop list supplies names for codes, without specifying the route order. The trip log records visits, rather than plans.

The draft below uses plan for the route card, sheet for both the route card and the stop list, and record for the trip log. Those mappings are supplied facts of this teaching exercise. In a real draft, an unresolved reference would need clarification before you could confidently rename it.

Repair the whole passage

Original draft:

“Before the walk, copy the planned stop codes onto the plan. Keep the sheet beside the plan to look up each stop name. During the walk, follow the sheet in its listed order. Afterward, write the codes you actually visited in the record.”

Finished passage:

“Before the walk, copy the planned stop codes onto the route card. Keep the stop list beside the route card to look up each stop name. During the walk, follow the route card in its listed order. Afterward, write the codes you actually visited in the trip log.”

The edit keeps the preparation, use and recordkeeping instructions intact. It does not make the stop list a second ordered route, or turn the planned route card into a record of completed visits.

Every old reference has an explicit destination:

• First plan, receiving the planned codes: route card.

• First sheet, used to look up stop names: stop list.

• Second plan, placed beside the stop list: route card.

• Second sheet, followed in its listed order: route card.

• Record, receiving the visited codes: trip log.

This is why a global replacement of sheet would fail. Replacing both occurrences with route card would lose the name lookup. Replacing both with stop list would assign the planned sequence to the wrong document. The supplied meaning of each occurrence determines its replacement.

Explain a useful outside alias once

The supplied fictional outside note says: “Use the itinerary to follow the planned sequence of stop codes.” In this exercise, its word itinerary refers only to the route card. It does not name a fourth document.

A finished bridge for the blog passage is: “The outside note calls the route card an itinerary. Here, itinerary means route card.” Continue with: “Follow the route card in its listed order.”

That bridge connects the note's wording with the article's chosen name. It preserves the outside wording rather than silently editing it. Apply the same care to exact source names, quoted text, code strings and actual interface labels: retain the wording readers need to recognize, then explain the relationship when necessary.

Keep consistency useful

My preference is stable names where an instruction depends on identifying the right thing. It is not a ban on synonyms throughout an article. An alias can help connect an outside source, while genuinely different objects still need distinct names.

Before changing a term, name its referent and check its contents. Then read the complete passage again: the preparation should still prepare, the lookup should still identify names, and the log should still record what happened. Do not resolve a missing definition by guessing.

Use your article brief to record necessary names before drafting. For the surrounding structure, follow how to write a blog post. The keyword research guide for bloggers helps you choose the reader question that the article should answer.