Globally say "Microsoft Edge Add-ons", without "store", "site", or "website"

[bhuvanapriyap]

You develop a Microsoft Edge extension, and then publish the extension at Microsoft Edge Add-ons.

Rendered article sections for review:

• Best practices for extensions

  • /extensions-chromium/developer-guide/best-practices.md
  • Internal preview: https://review.learn.microsoft.com/microsoft-edge/extensions-chromium/developer-guide/best-practices?branch=pr-en-us-3409
  • External preview: https://github.com/MicrosoftDocs/edge-developer/blob/bhuvanapriyap-patch-3/microsoft-edge/extensions-chromium/developer-guide/best-practices.md
  • Before/live: https://learn.microsoft.com/microsoft-edge/extensions-chromium/developer-guide/best-practices
  • The original commit scrubbed 'store' in this article.

• Curation and review process for extensions at Microsoft Edge Add-ons

  • /extensions-chromium/publish/add-ons-curation.md
  • Internal preview: https://review.learn.microsoft.com/microsoft-edge/extensions-chromium/publish/add-ons-curation?branch=pr-en-us-3409
  • External preview: https://github.com/MicrosoftDocs/edge-developer/blob/bhuvanapriyap-patch-3/microsoft-edge/extensions-chromium/publish/add-ons-curation.md
  • Before: https://learn.microsoft.com/microsoft-edge/extensions-chromium/publish/add-ons-store-curation
  • Planned live: https://learn.microsoft.com/microsoft-edge/extensions-chromium/publish/add-ons-curation
  • Changed filename from add-ons-store-curation.md to add-ons-curation.md.
    • Therefore the file appears as all-green in Files Changed.
    • Defined redirect from add-ons-store-curation.md to add-ons-curation.md (the word is visible in Address bar).
  • Changed title from Curation and review process for the Edge Add-ons store.
  • Made spot-fixes like in other files.
  • Defined "items" eg: "organizes items (such as themes, extensions, and apps)".

• Overview of Microsoft Edge extensions

  • /extensions-chromium/index.md
  • Internal preview: https://review.learn.microsoft.com/microsoft-edge/extensions-chromium/?branch=pr-en-us-3409
  • External preview: https://github.com/MicrosoftDocs/edge-developer/blob/bhuvanapriyap-patch-3/microsoft-edge/extensions-chromium/index.md
  • Before/live: https://learn.microsoft.com/microsoft-edge/extensions-chromium/
  • Some special handling.

• Global in repo

  • Changed to "at [Microsoft Edge Add-ons]", from variants such as "store" or "website".
  • Entire repo is now consistent.
  • Updated links.
  • Changed extensions docs links to relative-path format.
  • Standardized on "the Microsoft Edge extensions team".

Testing the redirect before merging:

Impl:

"source_path": "./microsoft-edge/extensions-chromium/publish/add-ons-store-curation.md",
"redirect_url": "/microsoft-edge/extensions-chromium/publish/add-ons-curation",

https://review.learn.microsoft.com/microsoft-edge/extensions-chromium/publish/add-ons-store-curation?branch=pr-en-us-3409
Expect to end up at url similar to:
https://review.learn.microsoft.com/microsoft-edge/extensions-chromium/publish/add-ons-curation?branch=pr-en-us-3409
Status: __
Ended up at: __

Testing the redirect after merging:

https://learn.microsoft.com/microsoft-edge/extensions-chromium/publish/add-ons-store-curation
Expect to end up at url similar to:
https://learn.microsoft.com/microsoft-edge/extensions-chromium/publish/add-ons-curation
Status: __
Ended up at: __

AB#56766281

[mikehoffms]

LGTM - Writer/Editor

[captainbrosset]

There's now a very clear distinction between when we use "extension" and when we use "add-ons". Thank you.

I left a few comments in the diff.

I also have a general comment that applies to many files: some articles now have many links to Microsoft Edge Add-ons. I know that consistently formatting all occurrences of this helps with maintainability, but having too many links within one article, or even one section may hurt readability by attracting too much attention to the same string over and over again.

I would almost suggest a rule like this: If Microsoft Edge Add-ons appears more than once in a single section (h2, h4, or h6), only link the first instance.

The first one would therefore be: at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com/addons), and subsequent ones would be at Microsoft Edge Add-ons.

[learn-build-service-prod]

Learn Build status updates of commit dcb2d5b:

💡 Validation status: suggestions

File	Status	Preview URL	Details
microsoft-edge/extensions-chromium/developer-guide/native-messaging.md	💡Suggestion	View	Details
.openpublishing.redirection.json	✅Succeeded	View
microsoft-edge/devtools-guide-chromium/customize/extensions.md	✅Succeeded	View
microsoft-edge/devtools-guide-chromium/whats-new/2023/01/devtools-109.md	✅Succeeded	View
microsoft-edge/devtools-guide-chromium/whats-new/2023/08/devtools-116.md	✅Succeeded	View
microsoft-edge/extensions-chromium/developer-guide/alternate-distribution-options.md	✅Succeeded	View
microsoft-edge/extensions-chromium/developer-guide/api-support.md	✅Succeeded	View
microsoft-edge/extensions-chromium/developer-guide/best-practices.md	✅Succeeded	View
microsoft-edge/extensions-chromium/developer-guide/csp.md	✅Succeeded	View
microsoft-edge/extensions-chromium/developer-guide/declare-permissions.md	✅Succeeded	View
microsoft-edge/extensions-chromium/developer-guide/manifest-v3.md	✅Succeeded	View
microsoft-edge/extensions-chromium/developer-guide/match-patterns.md	✅Succeeded	View
microsoft-edge/extensions-chromium/developer-guide/migrate-your-extension-from-manifest-v2-to-v3.md	✅Succeeded	View
microsoft-edge/extensions-chromium/developer-guide/minimize-page-load-time-impact.md	✅Succeeded	View
microsoft-edge/extensions-chromium/developer-guide/port-chrome-extension.md	✅Succeeded	View
microsoft-edge/extensions-chromium/developer-guide/run-compiled-code.md	✅Succeeded	View
microsoft-edge/extensions-chromium/getting-started/extension-sideloading.md	✅Succeeded	View
microsoft-edge/extensions-chromium/getting-started/picture-inserter-content-script.md	✅Succeeded	View
microsoft-edge/extensions-chromium/getting-started/picture-viewer-popup-webpage.md	✅Succeeded	View
microsoft-edge/extensions-chromium/index.md	✅Succeeded	View
microsoft-edge/extensions-chromium/landing/index.yml	✅Succeeded	View
microsoft-edge/extensions-chromium/publish/aad-account.md	✅Succeeded	View
microsoft-edge/extensions-chromium/publish/add-ons-curation.md	✅Succeeded	View
microsoft-edge/extensions-chromium/publish/add-ons-store-curation.md	✅Succeeded	n/a (file deleted or renamed)
microsoft-edge/extensions-chromium/publish/contact-extensions-team.md	✅Succeeded	View

This comment lists only the first 25 files in the pull request.

microsoft-edge/extensions-chromium/developer-guide/native-messaging.md

• Line 233, Column 3: [Suggestion: other-site-link-broken - See documentation] Link 'https://chromium.googlesource.com/chromium/src/+/HEAD/docs/user_data_dir.md' points to a page that doesn't exist. Check the path or URL and update the link.
• Line 253, Column 3: [Suggestion: other-site-link-broken - See documentation] Link 'https://chromium.googlesource.com/chromium/src/+/HEAD/docs/user_data_dir.md' points to a page that doesn't exist. Check the path or URL and update the link.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

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

[bhuvanapriyap]

Approved - LGTM-PM

[learn-build-service-prod]

Learn Build status updates of commit 6677039:

💡 Validation status: suggestions

File	Status	Preview URL	Details
microsoft-edge/extensions-chromium/developer-guide/native-messaging.md	💡Suggestion	View	Details
.openpublishing.redirection.json	✅Succeeded	View
microsoft-edge/devtools-guide-chromium/customize/extensions.md	✅Succeeded	View
microsoft-edge/devtools-guide-chromium/whats-new/2023/01/devtools-109.md	✅Succeeded	View
microsoft-edge/devtools-guide-chromium/whats-new/2023/08/devtools-116.md	✅Succeeded	View
microsoft-edge/extensions-chromium/developer-guide/alternate-distribution-options.md	✅Succeeded	View
microsoft-edge/extensions-chromium/developer-guide/api-support.md	✅Succeeded	View
microsoft-edge/extensions-chromium/developer-guide/best-practices.md	✅Succeeded	View
microsoft-edge/extensions-chromium/developer-guide/csp.md	✅Succeeded	View
microsoft-edge/extensions-chromium/developer-guide/declare-permissions.md	✅Succeeded	View
microsoft-edge/extensions-chromium/developer-guide/manifest-v3.md	✅Succeeded	View
microsoft-edge/extensions-chromium/developer-guide/match-patterns.md	✅Succeeded	View
microsoft-edge/extensions-chromium/developer-guide/migrate-your-extension-from-manifest-v2-to-v3.md	✅Succeeded	View
microsoft-edge/extensions-chromium/developer-guide/minimize-page-load-time-impact.md	✅Succeeded	View
microsoft-edge/extensions-chromium/developer-guide/port-chrome-extension.md	✅Succeeded	View
microsoft-edge/extensions-chromium/developer-guide/run-compiled-code.md	✅Succeeded	View
microsoft-edge/extensions-chromium/getting-started/extension-sideloading.md	✅Succeeded	View
microsoft-edge/extensions-chromium/getting-started/picture-inserter-content-script.md	✅Succeeded	View
microsoft-edge/extensions-chromium/getting-started/picture-viewer-popup-webpage.md	✅Succeeded	View
microsoft-edge/extensions-chromium/index.md	✅Succeeded	View
microsoft-edge/extensions-chromium/landing/index.yml	✅Succeeded	View
microsoft-edge/extensions-chromium/publish/aad-account.md	✅Succeeded	View
microsoft-edge/extensions-chromium/publish/add-ons-curation.md	✅Succeeded	View
microsoft-edge/extensions-chromium/publish/add-ons-store-curation.md	✅Succeeded	n/a (file deleted or renamed)
microsoft-edge/extensions-chromium/publish/contact-extensions-team.md	✅Succeeded	View

This comment lists only the first 25 files in the pull request.

microsoft-edge/extensions-chromium/developer-guide/native-messaging.md

• Line 233, Column 3: [Suggestion: other-site-link-broken - See documentation] Link 'https://chromium.googlesource.com/chromium/src/+/HEAD/docs/user_data_dir.md' points to a page that doesn't exist. Check the path or URL and update the link.
• Line 253, Column 3: [Suggestion: other-site-link-broken - See documentation] Link 'https://chromium.googlesource.com/chromium/src/+/HEAD/docs/user_data_dir.md' points to a page that doesn't exist. Check the path or URL and update the link.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

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