Fix Character Spelling in ContentType

[Tornhoof]

As suggested by @stephentoub in #66764 this PR fixes the two instances of tool-related spelling hiccups.

I did a cursory glance through other files via regex, but couldn't find any obvious other instances of such hiccups

[ghost]

Tagging subscribers to this area: @dotnet/area-system-io
See info in area-owners.md if you want to be subscribed.

Issue Details

---

As suggested by @stephentoub in #66764 this PR fixes the two instances of tool-related spelling hiccups.

I did a cursory glance through other files via regex, but couldn't find any obvious other instances of such hiccups

Author:	Tornhoof
Assignees:	-
Labels:	area-System.IO
Milestone:	-

[deeprobin]

LGTM

The pipeline is currently failing due to an internal infrastructure problem (https://github.com/dotnet/core-eng/issues/15812).

But since this PR only contains comment changes I don't see any risk to merge.

[stephentoub]

But since this PR only contains comment changes I don't see any risk to merge.

@deeprobin, why are you commenting on this PR about its mergability or risks from the PR?

[deeprobin]

But since this PR only contains comment changes I don't see any risk to merge.

@deeprobin, why are you commenting on this PR about its mergability or risks from the PR?

I look at the existing PRs every now and then when I have time and try to contribute (as long as they are not marked as no-review).

I wanted to point out that this PR does not carry any risks, because Helix currently has problems and therefore the jobs run on red.

[stephentoub]

I wanted to point out that this PR does not carry any risks, because Helix currently has problems and therefore the jobs run on red.

Thank you, but the maintainers of the repo are fully aware of both infrastructure issues that were in fight as well as the risk profile of a two-line comment-only change.