Fix ms.service: issues found in content engagement report

[msangapu-msft]

AB#49023826

[msangapu-msft]

@Reezaali can you please merge this? it's affecting our content engagement data for App Service.

[mikehoffms]

full-text search of repo on "ms.service:" reveals two instances to fix: docset landing page & devtools landing page. Then, all files will have same value (along w/ a valid value for ms.subservice if present/applicable). Pushed commits.

[msangapu-msft]

full-text search of repo on "ms.service:" reveals two instances to fix: docset landing page & devtools landing page. Then, all files will have same value (along w/ a valid value for ms.subservice if present/applicable). Pushed commits.

Thank you @mikehoffms

[learn-build-service-prod]

Learn Build status updates of commit 1f7b8e9:

✅ Validation status: passed

File	Status	Preview URL	Details
microsoft-edge/developer/index.yml	✅Succeeded	View
microsoft-edge/devtools-guide-chromium/landing/index.yml	✅Succeeded	View

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

[mikehoffms]

Approved the PR, after checked valid values for ms.service: & ms.subservice:, for hub page (ok) & the two landing pages (fixed).