MicrosoftDocs · mikehoffms · Nov 25, 2025 · Nov 24, 2025
diff --git a/microsoft-edge/extensions/contact.md b/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

diff --git a/microsoft-edge/extensions/developer-guide/port-chrome-extension.md b/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:[email protected]).
-
-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).
diff --git a/microsoft-edge/extensions/publish/publish-extension-images/add-a-language.png b/microsoft-edge/extensions/publish/publish-extension-images/add-a-language.png
diff --git a/microsoft-edge/extensions/publish/publish-extension-images/details-page.png b/microsoft-edge/extensions/publish/publish-extension-images/details-page.png
diff --git a/microsoft-edge/extensions/publish/publish-extension-images/duplicate-option.png b/microsoft-edge/extensions/publish/publish-extension-images/duplicate-option.png
diff --git a/microsoft-edge/extensions/publish/publish-extension-images/edit-details-icon.png b/microsoft-edge/extensions/publish/publish-extension-images/edit-details-icon.png
diff --git a/microsoft-edge/extensions/publish/publish-extension-images/generation-error.png b/microsoft-edge/extensions/publish/publish-extension-images/generation-error.png
diff --git a/microsoft-edge/extensions/publish/publish-extension-images/generation-limit.png b/microsoft-edge/extensions/publish/publish-extension-images/generation-limit.png
diff --git a/microsoft-edge/extensions/publish/publish-extension-images/generation.png b/microsoft-edge/extensions/publish/publish-extension-images/generation.png
diff --git a/...nsions/publish/publish-extension-images/store-listing-section-for-extension.png b/...nsions/publish/publish-extension-images/store-listing-section-for-extension.png
diff --git a/microsoft-edge/extensions/publish/publish-extension-images/store-listings-page.png b/microsoft-edge/extensions/publish/publish-extension-images/store-listings-page.png
diff --git a/microsoft-edge/extensions/publish/publish-extension.md b/microsoft-edge/extensions/publish/publish-extension.md
diff --git a/microsoft-edge/extensions/update/transfer-ownership.md b/microsoft-edge/extensions/update/transfer-ownership.md
@@ -12,6 +12,8 @@ ms.date: 11/14/2025
 
 As an extension developer, you can seamlessly transfer ownership of your Microsoft Edge extension to another party.  Transferring ownership of an extension can be essential for various reasons, such as organizational changes, project handovers, or streamlining management processes.  Your Microsoft Edge extension can continue to thrive under new ownership without any disruptions.
 
+<!-- email is only used for this task/article -->
+
 
 <!-- ====================================================================== -->
 ## Initiate the ownership transfer request
@@ -55,7 +57,7 @@ The Microsoft Edge extensions team will keep you informed of progress or any add
 
 This process typically takes approximately three weeks to complete, depending on the response times from all parties involved.
 
-For any questions, contact [[email protected]](mailto:[email protected]).
+For questions about this process, contact [[email protected]](mailto:[email protected]).
 
 
 <!-- ====================================================================== -->