BitConverter.ToString(byte[]) states being affected by endianness - how so?

The remarks of [`System.BitConverter.ToString()`](https://docs.microsoft.com/en-us/dotnet/api/system.bitconverter.tostring) state for all overloads of the method:

> All the elements of `value` are converted. The order of hexadecimal strings returned by the [ToString](https://docs.microsoft.com/en-us/dotnet/api/system.bitconverter.tostring) method depends on whether the computer architecture is little-endian or big-endian.

I don't understand how endianness can affect the outcome, since the [reference source](https://source.dot.net/#System.Private.CoreLib/BitConverter.cs,654) iterates over each element in the input byte array in order, then operates on them as single bytes, and converts each to its hexadecimal representation (interlaced with hyphens).

Where does endianness come into effect here, or is this remark incorrect / misleading?

Start with the System.BitConverter.ToString() API documentation and the referenced System.Private.CoreLib/BitConverter.cs source. Compare the documented endianness remark with the byte-array iteration shown there, then update the remark if the investigation confirms it is misleading and verify the rendered API text.

Scritto dal modello di indicizzazione a partire dal testo della issue.