From 3fbd79de5339b0fd0853973099a8843b84bc475a Mon Sep 17 00:00:00 2001 From: Takashi Takebayashi Date: Thu, 16 Jan 2025 10:25:36 +0900 Subject: [PATCH] Fix typo (#11678) StackOverflow -> Stack Overflow --- .../dev-cross-plat/resolving-dependency-conflicts.md | 2 +- .../dev-cross-plat/vscode/understanding-file-encoding.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/reference/docs-conceptual/dev-cross-plat/resolving-dependency-conflicts.md b/reference/docs-conceptual/dev-cross-plat/resolving-dependency-conflicts.md index b9be92770cc9..9299814608f8 100644 --- a/reference/docs-conceptual/dev-cross-plat/resolving-dependency-conflicts.md +++ b/reference/docs-conceptual/dev-cross-plat/resolving-dependency-conflicts.md @@ -875,7 +875,7 @@ jumping off points: - [.NET Framework: Best practices for assembly loading][24] - [.NET Framework: How the runtime locates assemblies][25] - [.NET Framework: Resolve assembly loads][26] -- [StackOverflow: Assembly binding redirect, how and why?][27] +- [Stack Overflow: Assembly binding redirect, how and why?][27] - [PowerShell: Discussion about implementing AssemblyLoadContexts][28] - [PowerShell: `Assembly.LoadFile()` doesn't load into default AssemblyLoadContext][29] - [Rick Strahl: When does a .NET assembly dependency get loaded?][30] diff --git a/reference/docs-conceptual/dev-cross-plat/vscode/understanding-file-encoding.md b/reference/docs-conceptual/dev-cross-plat/vscode/understanding-file-encoding.md index e62f74674bf6..ace74889f937 100644 --- a/reference/docs-conceptual/dev-cross-plat/vscode/understanding-file-encoding.md +++ b/reference/docs-conceptual/dev-cross-plat/vscode/understanding-file-encoding.md @@ -229,7 +229,7 @@ finally It's possible to configure PowerShell to use a given encoding more generally using profile settings. See the following articles: -- @mklement0's [answer about PowerShell encoding on StackOverflow][21]. +- @mklement0's [answer about PowerShell encoding on Stack Overflow][21]. - @rkeithhill's [blog post about dealing with BOM-less UTF-8 input in PowerShell][20]. It's not possible to force PowerShell to use a specific input encoding. PowerShell 5.1 and below, @@ -315,7 +315,7 @@ There are a few other nice posts on encoding and configuring encoding in PowerSh read: - [about_Character_Encoding][01] -- @mklement0's [summary of PowerShell encoding on StackOverflow][22] +- @mklement0's [summary of PowerShell encoding on Stack Overflow][22] - Previous issues opened on VS Code-PowerShell for encoding problems: - [#1308][12] - [#1628][13]