Update does-osquery-violate-the-new-york-employee-monitoring-law.md (#11247)

Fix github username for JD

# Checklist for submitter

If some of the following don't apply, delete the relevant line.

- [ ] Changes file added for user-visible changes in `changes/` or
`orbit/changes/`.
See [Changes
files](https://fleetdm.com/docs/contributing/committing-changes#changes-files)
for more information.
- [ ] Documented any API changes (docs/Using-Fleet/REST-API.md or
docs/Contributing/API-for-contributors.md)
- [ ] Documented any permissions changes
- [ ] Input data is properly validated, `SELECT *` is avoided, SQL
injection is prevented (using placeholders for values in statements)
- [ ] Added support on fleet's osquery simulator `cmd/osquery-perf` for
new osquery data ingestion features.
- [ ] Added/updated tests
- [ ] Manual QA for all new/changed functionality
  - For Orbit and Fleet Desktop changes:
- [ ] Manual QA must be performed in the three main OSs, macOS, Windows
and Linux.
- [ ] Auto-update manual QA, from released version of component to new
version (see [tools/tuf/test](../tools/tuf/test/README.md)).

articles/does-osquery-violate-the-new-york-employee-monitoring-law.md

@@ -96,6 +96,6 @@ That’s why we built Fleet Desktop (available on Windows, Linux, and macOS) to
 
 <meta name="category" value="security">
 <meta name="authorFullName" value="JD Strong">
-<meta name="authorGitHubUsername" value="spokanemac ">
+<meta name="authorGitHubUsername" value="spokanemac">
 <meta name="publishedOn" value="2023-04-18">
 <meta name="articleTitle" value="Does osquery violate the New York employee monitoring law?">