containerregistry - cspell found spelling errors in public API surface

[danieljurek]

Investigation for this PR: #23150 found spelling errors. When the linked PR merges this service will be opted out of public API surface spell checking to keep other PRs unblocked. This issue describes how to opt back in.

If the above linked PR has not merged this service is still opted out and not blocked by the detection of spelling errors in the public API surface.

What to do

1. Correct spelling errors or check in fixes for the false positives
2. Opt back into Public API surafe spell checking

Correct errors

To correct false positives or learn about spell checking see: https://aka.ms/azsdk/engsys/spellcheck

Spell Check Output

1/1 .\sdk\containerregistry\Azure.Containers.ContainerRegistry\api\Azure.Containers.ContainerRegistry.netstandard2.0.cs 1080.63ms X
D:\code\azure-sdk-for-net\sdk\containerregistry\Azure.Containers.ContainerRegistry\api\Azure.Containers.ContainerRegistry.netstandard2.0.cs:74:82 - Unknown word (Illumos)
CSpell: Files checked: 1, Issues found: 1 in 1 files

To check the public API surface locally, in the root of the repo run:

eng/scripts/Export-API.ps1 -ServiceDirectory containerregistry -SpellCheckPublicApiSurface

You may also need to set -SDKType if the appropriate value of SDKType is not all for the service.

Opt back in

NEW INSTRUCTIONS: In the .vscode/cspell.json file remove the line for your service (of the form "sdk/<service>/*/api/*.cs") from the ignorePaths section and check in the change.

OLD INSTRUCTIONS: In the ci.yml file for this service, remove the line: SpellCheckPublicApiSurface: false

[AlexGhiondea]

@danieljurek is there a way to add this work to an allow list? The name that is flagged represents a known unix distro.

[Mohit-Chakraborty]

We can follow one of the documented steps to handle this false positive.
I'll assign this issue to myself for the cleanup.