Reclassify ms.topic values batch 2 (entries 41 to 68).

[Copilot]

Reclassified 28 markdown files from legacy article and conceptual topic types to modern, semantically accurate classifications based on content analysis.

Changes by Topic Type

21 files → concept-article

• Orleans: timers/reminders, Aspire integration, clients, activation collection, grain directory, cluster management, lifecycle, scheduler, streaming
• .NET: string comparison, parsing, type conversion, regex behavior and object model

3 files → reference

• Regular expression syntax documentation: character escapes, miscellaneous constructs, substitutions

2 files → how-to

• Orleans transactions setup, PowerShell client installation

2 files → best-practice

• Display/persist formatted data, command-line design guidance

Each file modified: replaced single ms.topic value in frontmatter. No duplicate entries.

Original prompt

For the pull request title, you MUST use: "Reclassify ms.topic values batch 2 (entries 41 to 68)."

Get the entire contents of each markdown file up to a maximum of 300 lines, not just a portion. Ignore lines for title and description and classify the content into one of the following topics, based on the associated descriptions of each topic.

Here's a markdown table defining each topic type:

Slug	Definition
best-practice	Offers best practices recommendations for working with a service or feature.
concept-article	Provides an in-depth explanation of functionality, features, or components related to a service(s) that is fundamental to understanding and use. It describes what something is, what it does, and how it works at a conceptual level. The article may include code examples, commands, SQL statements, Kusto queries, PowerShell scripts, or configuration syntax to illustrate concepts, but these are presented as REFERENCE EXAMPLES showing "this is the syntax" or "this is what it looks like," NOT as a task-based sequence the user must follow. CRITICAL CODE EXAMPLE TEST: If an article shows code/queries under headings like "Examples," "Sample queries," or "Code samples" WITHOUT surrounding numbered procedural steps ("Step 1: Open... Step 2: Paste... Step 3: Run..."), that is concept-article, NOT how-to. The mere presence of code blocks does NOT make an article how-to. It shouldn't contain step-by-step procedural instructions for the user to follow, but might explain a high-level process flow and provide examples. It also shouldn't be task-oriented with explicit action items. May include bulleted lists describing what a feature or service does/can do without instructing the user how to do it. The system/feature is the subject being explained, not the user performing tasks. CRITICAL: If an article contains 2+ numbered steps, a Requirements or Prerequisites section, or imperatives directing user actions ("Ensure...", "Make sure to...", "Give permission...") that represent the PRIMARY purpose of the article, classify it as how-to even if other sections provide navigation or overview content.
end-user-help	Aimed at end users that provides a resolution on a specific issue.
error-reference	Reference content that documents error codes.
faq	Question-and-answer formatted content. (Has a .yml template.)
get-started	Helps users get started using a particular product or service. It's a basic high-level task to use as a proof-of-concept in a short timeframe.
glossary	Lists relevant terms for understanding and using a product, service, or scenario.
how-to	Contains numbered or bulleted PROCEDURAL STEPS that guide the customer through completing a specific task in sequence. The article's PRIMARY PURPOSE must be task completion with the user as the actor. The article must present steps in a clear sequential format (1, 2, 3... or Step 1 then Step 2... or 1, 1, 1...) that users follow in order to accomplish a goal. Steps must include imperative verbs directing user actions (e.g., "Click here," "Select," "Navigate to," "Enter this value," "Run this command," "Create a resource"). The user performs the steps, not just reads about what a system does. CRITICAL DISTINCTION: Illustrative syntax examples (showing what a command or query looks like) are NOT procedural steps. An article that shows Kusto queries, SQL statements, PowerShell scripts, or code samples under an "Examples" heading WITHOUT wrapping them in numbered procedural steps is concept-article, NOT how-to. The test is: "Is the user being walked through a sequence of actions?" If the article simply presents code/queries as reference material ("here's what this query looks like") without procedural context ("Step 1: Open the portal. Step 2: Navigate to... Step 3: Paste this query and click Run"), it is concept-article. A how-to article walks you through a process: "First do X, then do Y, then do Z." Code/command examples shown for reference or illustration without surrounding procedural context are concept-article, not how-to. Lists of capabilities or features that a tool performs are NOT how-to content, even if bulleted or numbered. CRITICAL: If an article contains 2+ numbered steps WITH task-oriented imperatives, or action-directing imperatives ("Ensure...", "Make sure to...", "Give permission...") that collectively represent the PRIMARY PURPOSE, classify as how-to. The presence of extensive procedural guidance (especially Prerequisites + numbered steps + imperatives forming a workflow) overrides other types. But if the article primarily explains a feature and includes a few syntax examples without procedural context, it's concept-article.
install-set-up-deploy	Provides the basic structure of a Install, set up, deploy article pattern that contains numbered procedural steps. This topic type can contain some conceptual information.
limits-and-quotas	Lists out the exte...

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.