Spelling - sqlserver

[jsoref]

Misspellings identified by the check-spelling action.

Split from #7507 - the sqlserver parts per #7507 (comment)

Required for all PRs:

• Signed CLA.

• Associated README.md updated. -- I'm going to wait for someone to review this before I take this step. Note that CONTRIBUTING.md makes no mention of this.

• Has appropriate unit tests. -- Not included, but available (note that it wouldn't be a make thing, although I suppose I could create a Docker for it... that seems pretty doable -- people have asked for a way to do that...):

  It reported: jsoref@25d89f6#commitcomment-39074475

  And it validated that the changes in this PR made it happy: jsoref@95180ce

---

Some projects like to rebase, some to squash, some ask for things to be split up. I try to avoid doing anything until a reviewer provides direction. It's much easier for me to initially work with individual commits (e.g. there are some en-US commits here, if you tell me your project is en-GB, I can easily drop them today, but if I squash eagerly, then disentangling them can be painful). I'm happy to make changes/follow directions within reason.

[jsoref]

@Trovalo

[Trovalo]

Here is the list of the impacts:

• Preemptive CPU Usage (time) - field key, no impact (it's never extracted in any case because of the query itself (bug), therefore it won't break anything)
• total_elapsed_time_ms - field key, will change measurement structure
• HADR_FILESTREAM_IOMGR_IOCOMPLETION - this fixes the version 1 of SQL Server queries, as a result. points with tag wait_type "HADR_FILESTREAM_IOMGR_IOCOMPLETION" will be excluded in the final result (it's not a relevant wait stat)
• PVTTable - internal name never exposed, no impact

To me this can be approved