Benefits of unsafe code are ambiguously stated (#47073)

* Initial plan

* Clarify that unsafe code enables performance optimizations rather than providing them automatically

Co-authored-by: BillWagner <493969+BillWagner@users.noreply.github.com>

* Fix wording to address review feedback - focus on direct memory access capabilities rather than algorithms

Co-authored-by: jkotas <6668460+jkotas@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: BillWagner <493969+BillWagner@users.noreply.github.com>
Co-authored-by: jkotas <6668460+jkotas@users.noreply.github.com>

Author: 3 people

docs/csharp/language-reference/unsafe-code.md

@@ -22,7 +22,7 @@ C# supports an [`unsafe`](keywords/unsafe.md) context, in which you can write *u
 Unsafe code has the following properties:
 
 - Methods, types, and code blocks can be defined as unsafe.
-- In some cases, unsafe code can increase an application's performance by removing array bounds checks.
+- In some cases, unsafe code can increase an application's performance by enabling direct memory access through pointers to avoid array bounds checks.
 - Unsafe code is required when you call native functions that require pointers.
 - Using unsafe code introduces security and stability risks.
 - The code that contains unsafe blocks must be compiled with the [**AllowUnsafeBlocks**](compiler-options/language.md#allowunsafeblocks) compiler option.