Resolve malformed dates in metadata

[Rageking8]

Fix malformed dates together with some light formatting works. All rectified dates were unambiguously derived using git history.

[prmerger-automator]

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

[learn-build-service-prod]

Learn Build status updates of commit 24bb923:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/communication-services/how-tos/calling-sdk/includes/closed-captions/closed-captions-teams-interop-android.md	✅Succeeded
articles/communication-services/how-tos/calling-sdk/includes/closed-captions/closed-captions-teams-interop-ios.md	✅Succeeded
articles/communication-services/how-tos/calling-sdk/includes/closed-captions/closed-captions-teams-interop-web.md	✅Succeeded
articles/communication-services/how-tos/calling-sdk/includes/closed-captions/closed-captions-teams-interop-windows.md	✅Succeeded
articles/security/fundamentals/index.yml	✅Succeeded
articles/sentinel/includes/unified-soc-preview-without-alert.md	✅Succeeded
includes/data-box-edge-gateway-port-config.md	✅Succeeded
includes/functions-flex-supported-regions-cli.md	✅Succeeded
includes/storsimple-virtual-device-security.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
Yaml File(s)	This PR includes changes to .yml file(s) owned by another author.

[ttorble]

@msmbaldwin @cwatson-cat @stevenmatthew @valindrae

Can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

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