Update "Publish a Microsoft Edge extension" (#3645)

* a few of the mods

* apply Word changes & writer/editor pass

* your>the extension

* your>the extension [2]

* porting - link text

* first, port it

* not "during your submission process"

* email in Contact article

* del 'asset'

* inc review anss

* structural edit Port

* Update store-listings-page.png

* update pngs & fields

* gen ai

* condense section

* singular

* not understand

* generation-error.png

* red box thin

* swapped pngs

* Optional

* .zip

* not English

* fail > not pass

* linkfix

* Detailed contents

* remaining .zip's

* dup Optional key/guide

* Fix any form field errors

* h2 store listing details for each language

* API is for code not P C

* your extension's code

* s5 linkfix

* fix first 2 h2s

* para1

* not "drag drop"

* all h2 are Steps

* just Support

* link

* generate pngs source

* redbox

Author: mikehoffms

microsoft-edge/extensions/contact.md

@@ -12,6 +12,8 @@ ms.date: 05/30/2025
 
 You can contact the Microsoft Edge extensions support team to request help, submit feedback, or report a copyright or trademark infringement.
 
+<!-- email is only used for [Transfer ownership of an extension](./update/transfer-ownership.md) -->
+
 
 <!-- ====================================================================== -->
 ## Issues page in the MicrosoftEdge-Extensions repo

microsoft-edge/extensions/developer-guide/port-chrome-extension.md

@@ -16,17 +16,17 @@ To port your Chrome extension:
 
 1. Review the Chrome extension APIs used in your extensions with the Microsoft Edge extensions [supported APIs](api-support.md) list.
 
-   If your extension uses APIs that aren't supported by Microsoft Edge, it might not port directly.
+   If the extension uses APIs that aren't supported by Microsoft Edge, it might not port directly.
 
 1. Remove the `update_url` field from the manifest file.
 
-1. If `Chrome` is used in either the name or the description of your extension, rebrand your extension using `Microsoft Edge`.  To pass the certification process, the changes are required.
+1. If `Chrome` is used in either the name or the description of your extension, rebrand the extension using `Microsoft Edge`.  To pass the certification process, the changes are required.
 
-1. Test your extension to check if it works in Microsoft Edge by [sideloading your extension](../getting-started/extension-sideloading.md).
+1. Test the extension to check if it works in Microsoft Edge by sideloading the extension.  See [Sideload an extension to install and test it locally](../getting-started/extension-sideloading.md).
 
-1. If you face any issues, you can debug your extensions in Microsoft Edge by using the DevTools, or [contact us](mailto:ext_dev_support@microsoft.com).
-
-1. Follow the [publishing guidelines](../publish/publish-extension.md) to publish your extension at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com).
+1. If you encounter any issues, you can:
+   * Debug the extension in Microsoft Edge by using DevTools; see [Overview of DevTools](../../devtools/overview.md).
+   * [Contact the Microsoft Edge extensions team](../contact.md).
 
 
 <!-- ====================================================================== -->
@@ -36,8 +36,10 @@ If your extension exchanges messages with a native app by using `chrome.runtime.
 
 
 <!-- ====================================================================== -->
-## Next steps
+## Publish the extension
 
 After your extension package is ready to publish at [Microsoft Edge Add-ons](https://microsoftedge.microsoft.com):
-1. [Register as a Microsoft Edge extension developer](../publish/create-dev-account.md)
-1. [Publish a Microsoft Edge extension](../publish/publish-extension.md)
+
+1. [Register as a Microsoft Edge extension developer](../publish/create-dev-account.md).
+
+1. [Publish a Microsoft Edge extension](../publish/publish-extension.md).