Tweak nolock function descriptions

[Rageking8]

The wording "locking the thread" seems a little off since it should either be "locking the stream" or some other "item". Omitting the "item" being locked seems to work the best at the expense of being less "specific" (as compared to using the phrase "locking the stream" etc). The large majority of locking for the normal analog of _nolock APIs are done via _lock_file with a FILE* for the stream, with some others being done via __acrt_lock with __acrt_conio_lock of type __acrt_lock_id (both locking functions are implemented using EnterCriticalSection) (the term "locking the stream" cannot be used for all _nolock APIs). Hence, using the generic term "without locking" for all applicable _nolock APIs make things uniform and the idea of "not locking" is decently conveyed.

@TylerMSFT Does this sound like an improvement? Happy to hear some feedback.

Note 1) Some descriptions (e.g. _fseek_nolock) are identical to their normal analog, therefore the notion of "not locking" is added.

Note 2) The descriptions of _getdcwd_nolock and _wgetdcwd_nolock are not modified as they are just macros to the normal analog.

[prmerger-automator]

@Rageking8 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit 3796953:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/c-runtime-library/reference/fclose-nolock.md	✅Succeeded
docs/c-runtime-library/reference/fflush-nolock.md	✅Succeeded
docs/c-runtime-library/reference/fgetc-nolock-fgetwc-nolock.md	✅Succeeded
docs/c-runtime-library/reference/fputc-nolock-fputwc-nolock.md	✅Succeeded
docs/c-runtime-library/reference/fread-nolock.md	✅Succeeded
docs/c-runtime-library/reference/fread-nolock-s2.md	✅Succeeded
docs/c-runtime-library/reference/fseek-nolock-fseeki64-nolock.md	✅Succeeded
docs/c-runtime-library/reference/ftell-nolock-ftelli64-nolock.md	✅Succeeded
docs/c-runtime-library/reference/fwrite-nolock.md	✅Succeeded
docs/c-runtime-library/reference/getchar-nolock-getwchar-nolock.md	✅Succeeded
docs/c-runtime-library/reference/getche-nolock-getwche-nolock.md	✅Succeeded
docs/c-runtime-library/reference/getch-nolock-getwch-nolock.md	✅Succeeded
docs/c-runtime-library/reference/getc-nolock-getwc-nolock.md	✅Succeeded
docs/c-runtime-library/reference/getdcwd-nolock-wgetdcwd-nolock.md	✅Succeeded
docs/c-runtime-library/reference/putchar-nolock-putwchar-nolock.md	✅Succeeded
docs/c-runtime-library/reference/putch-nolock-putwch-nolock.md	✅Succeeded
docs/c-runtime-library/reference/putc-nolock-putwc-nolock.md	✅Succeeded
docs/c-runtime-library/reference/ungetch-ungetwch-ungetch-nolock-ungetwch-nolock.md	✅Succeeded
docs/c-runtime-library/reference/ungetc-nolock-ungetwc-nolock.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[prmerger-automator]

PRMerger Results

Issue	Description
Changed Files	This PR contains more than 10 changed files.

[learn-build-service-prod]

Learn Build status updates of commit f5a3d28:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/c-runtime-library/reference/fclose-nolock.md	✅Succeeded
docs/c-runtime-library/reference/fflush-nolock.md	✅Succeeded
docs/c-runtime-library/reference/fgetc-nolock-fgetwc-nolock.md	✅Succeeded
docs/c-runtime-library/reference/fputc-nolock-fputwc-nolock.md	✅Succeeded
docs/c-runtime-library/reference/fread-nolock.md	✅Succeeded
docs/c-runtime-library/reference/fread-nolock-s2.md	✅Succeeded
docs/c-runtime-library/reference/fseek-nolock-fseeki64-nolock.md	✅Succeeded
docs/c-runtime-library/reference/ftell-nolock-ftelli64-nolock.md	✅Succeeded
docs/c-runtime-library/reference/fwrite-nolock.md	✅Succeeded
docs/c-runtime-library/reference/getchar-nolock-getwchar-nolock.md	✅Succeeded
docs/c-runtime-library/reference/getche-nolock-getwche-nolock.md	✅Succeeded
docs/c-runtime-library/reference/getch-nolock-getwch-nolock.md	✅Succeeded
docs/c-runtime-library/reference/getc-nolock-getwc-nolock.md	✅Succeeded
docs/c-runtime-library/reference/getdcwd-nolock-wgetdcwd-nolock.md	✅Succeeded
docs/c-runtime-library/reference/putchar-nolock-putwchar-nolock.md	✅Succeeded
docs/c-runtime-library/reference/putch-nolock-putwch-nolock.md	✅Succeeded
docs/c-runtime-library/reference/putc-nolock-putwc-nolock.md	✅Succeeded
docs/c-runtime-library/reference/ungetch-ungetwch-ungetch-nolock-ungetwch-nolock.md	✅Succeeded
docs/c-runtime-library/reference/ungetc-nolock-ungetwc-nolock.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[prmerger-automator]

PRMerger Results

Issue	Description
Changed Files	This PR contains more than 10 changed files.

[Rageking8]

Reverted the addition of "without locking" as this article holds both normal and nolock variants of ungetch.

[Court72]

@TylerMSFT

Can you review the proposed changes?

When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[TylerMSFT]

I agree with you. I think this is an improvement and that being less prescriptive about what exactly is being locked is clearer. Developers will know what locking means in this content.
Thank you for these updates.

[TylerMSFT]

#sign-off