#BE7511 - publish rename

docs/account/my-organization/artifacts/retention-period.md

@@ -76,8 +76,8 @@ Automatically deletes **undistributed artifacts** that exceed the defined retent
 
 **Publish to Stores** module includes specific rules for artifacts:
 
-#### Delete Publish Module Artifacts
-Automatically deletes artifacts within the Publish to Stores module profiles that are older than the retention period.
+#### Delete Publish to Stores Artifacts
+Automatically deletes artifacts that have been **published** and are older than the retention period.
 
 #### Keep if Marked as RC
 When enabled, preserves artifacts marked as **Release Candidate (RC)** even if they exceed the retention period.

docs/account/my-organization/billing/index.md

@@ -24,7 +24,7 @@ The Billing section allows you to monitor your usage summary, including builds,
 - **[Builds](/build/build-process-management/manual-builds)** : Number of builds initiated from the build module in a single billing cycle.
 - **[Code Push Updates](/code-push)** : The number of devices receiving CodePush updates within a single billing cycle.
 - **[Testing Distribution](/testing-distribution/testing-portal)** : Number of app downloads from the Testing Portal in a single billing cycle.
-- **[Publishes](/publish-module)** : Number of publishes initiated from the Publish module in a single billing cycle.
+- **[Publishes](/publish-module)** : Number of publishes initiated from the Publish to Stores in a single billing cycle.
 - **[Enterprise App Store](/enterprise-app-store/enterprise-portal)** : Number of app downloads from the Enterprise App Store in a single billing cycle.
 - **[Team Members](/account/my-organization/profile-and-team/team-management)** : Number of team members allowed in a single organization.
 - **[Artifact Storage](/account/my-organization/artifacts)** : Total storage size for all the build and distribution artifacts across the platform.

docs/account/my-organization/profile-and-team/role-management.md

@@ -40,7 +40,7 @@ Some role types are not used in certain modules because they are redundant or un
 
 When assigning roles on Appcircle, you can assign more than one role for a user at the same time. For example, a user can be both **Manager** and **Operator** in the Build module.
 
-For this reason, Appcircle behavior will change when multiple roles are assigned. For example, you have assigned **Ext Operator** and **Viewer** role in **Publish Module** for a user. This means that the Ext Operator role now has the privileges of the Viewer role. So while Ext Operator cannot see Activity logs, it now has access to those logs because it also has the viewer role.
+For this reason, Appcircle behavior will change when multiple roles are assigned. For example, you have assigned **Ext Operator** and **Viewer** role in **Publish to Stores** for a user. This means that the Ext Operator role now has the privileges of the Viewer role. So while Ext Operator cannot see Activity logs, it now has access to those logs because it also has the viewer role.
 
 :::
 
@@ -221,7 +221,7 @@ The following table details the roles and restrictions for the [**Testing Groups
 | Testing Groups | List LDAP Groups and Members              | ✅     | ✅       | ✅      |
 
 
-### Publish Module iOS Permissions
+### Publish to Stores iOS Permissions
 
 The following table details the roles and restrictions for the [**Publish**](/publish-module) module for iOS. Please refer to the related module information and caution notes.
 
@@ -265,7 +265,7 @@ User can resign the binary if this user has **Manager** or **Viewer** Signing Id
 :::
 
 
-### Publish Module Android Permissions
+### Publish to Stores Android Permissions
 
 The following table details the roles and restrictions for the [**Publish**](/publish-module) module for Android. Please refer to the related modules information and caution notes.
 

docs/account/my-organization/security/credentials/adding-an-app-store-connect-api-key.md

@@ -122,7 +122,7 @@ Once the API key is generated, it must be added to Appcircle:
 6.	Click Save to complete the setup.
 
 :::info
-Please note that the registered Enterprise API Key cannot be used within the Publish module because the Apple Enterprise Program does not provide TestFlight or App Store Connect services.
+Please note that the registered Enterprise API Key cannot be used within the Publish to Stores because the Apple Enterprise Program does not provide TestFlight or App Store Connect services.
 :::
 
 ## Sharing App Store Connect Credentials

docs/build/build-process-management/configurations.md

@@ -185,7 +185,7 @@ Enabling "Automatically Distribute to Publish" will display the available [Publi
 
 Simply select your relevant publish profiles, and Appcircle will automatically send your builds to the selected publish profiles.
 
-Please note that the publish profiles should be created within the publish module prior to configuring the distribution settings in the build profile.
+Please note that the publish profiles should be created within the Publish to Stores prior to configuring the distribution settings in the build profile.
 
 #### Send to Enterprise App Store
 

docs/enterprise-app-store/enterprise-app-store-profile.md

@@ -15,7 +15,7 @@ The Enterprise App Store provides a centralized platform for managing an organiz
 
 ## Creating a Profile
 
-An Enterprise build profile can be created in several ways. IPA or APK files can either be manually uploaded or sent from Appcircle’s Distribution, Build, or Publish modules.
+An Enterprise build profile can be created in several ways. IPA or APK files can either be manually uploaded or sent from Appcircle’s Distribution, Build, or Publish to Storess.
 
 ## Uploading Binary
 
@@ -49,7 +49,7 @@ Binaries can also be uploaded via the Build module. For more information, please
 
 Binaries can also be uploaded via the Testing Distribution module. For more information, please visit the [Testing Distribution](/testing-distribution/create-or-select-a-distribution-profile#send-your-application-to-enterprise-app-store) documentation.
 
-### Upload via Publish Module
+### Upload via Publish to Stores module
 
 The Publish Flow steps can be customized to send the binary to the Enterprise App Store. For more information, please visit the [Publish Integrations](/publish-integrations/common-publish-integrations/send-to-enterprise-app-store) documentation.
 

docs/enterprise-app-store/index.md

@@ -29,7 +29,7 @@ For a complete overview of the Appcircle Enterprise App Store module capabilitie
 
 ## [Enterprise App Store Profile](/enterprise-app-store/enterprise-app-store-profile)
 
-There are several ways to create an Enterprise App Store Profile. You can either manually upload your IPA or APK files or send them through Appcircle's Distribution, Build, or Publish modules.
+There are several ways to create an Enterprise App Store Profile. You can either manually upload your IPA or APK files or send them through Appcircle's Distribution, Build, or Publish to Stores modules.
 
 <ContentRef url="/enterprise-app-store/enterprise-app-store-profile">Enterprise App Store Profile]</ContentRef>
 

docs/publish-integrations/android-publish-integrations/index.md

@@ -8,7 +8,7 @@ tags: [android, android integrations, android publish integrations]
 
 Appcircle's Android Integrations facilitate the distribution of your Android applications to major app stores with minimal effort.
 
-To use the Android Integration, click on the **Android Publish** button on the left in the Publish module.
+To use the Android Integration, click on the **Android Publish** button on the left in the Publish to Stores module.
 
 <Screenshot url='https://cdn.appcircle.io/docs/assets/publish-leftbar-android.png' />
 

docs/publish-integrations/android-publish-integrations/publish-to-google-play.md

@@ -1,6 +1,6 @@
 ---
 title: Publish to Google Play
-description: Publish your Android applications to the Google Play Store with Appcircle's Publish module.
+description: Publish your Android applications to the Google Play Store with Appcircle's Publish to Stores module.
 tags: [android, publish google play, android publish integrations]
 sidebar_position: 2
 ---
@@ -11,7 +11,7 @@ import RunnerUsage from '@site/docs/\_publish-steps-runner-usage-caution.mdx';
 
 # Publish to Google Play
 
-Appcircle supports sending APK and AAB binaries to [Google Play](https://play.google.com) through the Publish module.
+Appcircle supports sending APK and AAB binaries to [Google Play](https://play.google.com) through the Publish to Stores module.
 
 Google Play no longer supports APK submission; however, Appcircle retains the APK submission feature for exceptional cases. For more details about APK submission, please refer to this document:
 > [Google Play requires new apps to be published with the Android App Bundle starting August 2021.](https://android-developers.googleblog.com/2021/06/the-future-of-android-app-bundles-is.html)

docs/publish-integrations/android-publish-integrations/publish-to-huawei-appgallery.md

@@ -11,7 +11,7 @@ import RunnerUsage from '@site/docs/\_publish-steps-runner-usage-caution.mdx';
 
 # Publish to Huawei AppGallery
 
-Appcircle supports sending [APK](https://developer.huawei.com/consumer/en/doc/app/agc-help-releaseapkrpk-0000001106463276) and [AAB](https://developer.huawei.com/consumer/en/doc/app/agc-help-releasebundle-0000001100316672) binaries to [Huawei AppGallery](https://appgallery.huawei.com/) through the Publish module.
+Appcircle supports sending [APK](https://developer.huawei.com/consumer/en/doc/app/agc-help-releaseapkrpk-0000001106463276) and [AAB](https://developer.huawei.com/consumer/en/doc/app/agc-help-releasebundle-0000001100316672) binaries to [Huawei AppGallery](https://appgallery.huawei.com/) through the Publish to Stores module.
 
 <RunnerUsage />
 

docs/publish-integrations/common-publish-integrations/get-approval-via-email.md

@@ -40,7 +40,7 @@ For example, imagine you need approval from at least two people to keep the flow
 
 ### Email Template
 
-With the Email Approval step provided by the Appcircle Publish module, release processes are managed in a structured and controlled way. The email includes all key information, such as binary details, release notes, and other relevant data, so users can review the release context without needing to search within the Appcircle interface.
+With the Email Approval step provided by the Appcircle Publish to Stores module, release processes are managed in a structured and controlled way. The email includes all key information, such as binary details, release notes, and other relevant data, so users can review the release context without needing to search within the Appcircle interface.
 
 To proceed with the approval, users can click the link in the email, which opens the binary details window in Appcircle. From this view, they can examine version information, build details, and commit history before making a decision by selecting **Approve** or **Reject**.
 

docs/publish-integrations/common-publish-integrations/index.md

@@ -39,7 +39,7 @@ Appcircle's integration tools are designed to simplify and automate the publishi
 
 ## [Send to Testing Distribution](/publish-integrations/common-publish-integrations/send-to-testing-distribution)
 
-With Appcircle's Publish module, you can submit your application to external stores such as App Store, Google Play, Huawei AppGallery or Microsoft Intune, as well as to Appcircle's Testing Distribution module.
+With Appcircle's Publish to Stores module, you can submit your application to external stores such as App Store, Google Play, Huawei AppGallery or Microsoft Intune, as well as to Appcircle's Testing Distribution module.
 
 Testing Distribution module allows you to distribute your application without the need for any external tools.
 

docs/publish-integrations/common-publish-integrations/metadata-approval.md

@@ -23,7 +23,7 @@ When this step runs in your workflow, Appcircle sends a unique approval email to
 
 :::caution Metadata Approval Panel
 
-Access to the Metadata Approval Panel is **exclusively** available via the link sent in the approval email; it is **not** accessible through the standard Publish module UI.
+Access to the Metadata Approval Panel is **exclusively** available via the link sent in the approval email; it is **not** accessible through the standard Publish to Stores module UI.
 
 :::
 

docs/publish-integrations/common-publish-integrations/send-email.md

@@ -66,7 +66,7 @@ You can dynamically populate subject and content using environment variables. Th
 
 ### Creating Environment Variables
 
-First, you need to define the environment variables. To do this, go to the Publish module and select Publish Variables. From there, you can start creating the variables for your email settings.
+First, you need to define the environment variables. To do this, go to the Publish to Stores module and select Publish Variables. From there, you can start creating the variables for your email settings.
 
 <Screenshot url='https://cdn.appcircle.io/docs/assets/BE6186-email6.png' />
 

docs/publish-integrations/common-publish-integrations/send-to-enterprise-app-store.md

@@ -1,6 +1,6 @@
 ---
 title: Send to Enterprise App Store
-description: Learn how to send Binary to Enterprise App Store in the Publish module of Appcircle
+description: Learn how to send Binary to Enterprise App Store in the Publish to Stores module of Appcircle
 tags: [publish, publish module, enterprise, app store, enterprise app store, review]
 sidebar_position: 4
 ---
@@ -10,7 +10,7 @@ import NoRunnerUsage from '@site/docs/\_publish-steps-runner-no-usage-info.mdx';
 
 # Send to Enterprise App Store
 
-With Appcircle's Publish module, you can submit your application to external stores such as App Store, Google Play, Huawei AppGallery or Microsoft Intune, as well as to Appcircle's Enterprise App Store module.
+With Appcircle's Publish to Stores module, you can submit your application to external stores such as App Store, Google Play, Huawei AppGallery or Microsoft Intune, as well as to Appcircle's Enterprise App Store module.
 
 Enterprise App Store offers a store structure that you can use and customise for internal application distribution. For detailed information, please see the [**Enterprise App Store document**](/enterprise-app-store).
 

docs/publish-integrations/common-publish-integrations/send-to-testing-distribution.md

@@ -1,6 +1,6 @@
 ---
 title: Send to Testing Distribution
-description: Learn how to send Binary to Testing Distribution in the Publish module of Appcircle
+description: Learn how to send Binary to Testing Distribution in the Publish to Stores module of Appcircle
 tags: [publish, publish module, distribution, testing distribution]
 sidebar_position: 4
 ---
@@ -10,7 +10,7 @@ import NoRunnerUsage from '@site/docs/\_publish-steps-runner-no-usage-info.mdx';
 
 # Send to Testing Distribution
 
-With Appcircle's Publish module, you can submit your application to external stores such as App Store, Google Play, Huawei AppGallery or Microsoft Intune, as well as to Appcircle's Testing Distribution module.
+With Appcircle's Publish to Stores module, you can submit your application to external stores such as App Store, Google Play, Huawei AppGallery or Microsoft Intune, as well as to Appcircle's Testing Distribution module.
 
 Testing Distribution module allows you to distribute your application without the need for any external tools. For detailed information, please see the [**Testing Distribution Documentation**](/testing-distribution).
 

docs/publish-integrations/ios-publish-integrations/add-for-review-on-app-store.md

@@ -10,7 +10,7 @@ import RunnerUsage from '@site/docs/\_publish-steps-runner-usage-caution.mdx';
 
 # Add for Review on App Store
 
-Appcircle Publish Module isolates the user to a great extent in the App Store Connect interface with its steps. This allows you to manage the publishing process from a single location.. With the Add for Review on App Store step, you can send your application version in TestFlight directly for review.
+Appcircle Publish to Stores module isolates the user to a great extent in the App Store Connect interface with its steps. This allows you to manage the publishing process from a single location.. With the Add for Review on App Store step, you can send your application version in TestFlight directly for review.
 
 <RunnerUsage />
 

docs/publish-integrations/ios-publish-integrations/app-information-app-store.md

@@ -25,7 +25,7 @@ Below are brief descriptions of the information provided on the App Information
 | **App Name**         | The display name of the application on the selected platform.                                                                                                                                                                                                                       |                                                                                                         |
 | **Version**          | The current available app versions. For example, `1.0.5`.                                                                                                                                                                                                                           |                                                                                                         |
 | **Build Number**     | Version code information of your application. For example, `1.0.5(1)`.                                                                                                                                                                                                              |                                                                                                         |
-| **Uploaded Date**    | Date the application was first uploaded. The **Release Candidate** version is based on the date it was uploaded to the **Publish module**.                                                                                                                                          |                                                                                                         |
+| **Uploaded Date**    | Date the application was first uploaded. The **Release Candidate** version is based on the date it was uploaded to the **Publish to Stores module**.                                                                                                                                          |                                                                                                         |
 | **Expire Date**      | The expiration date of the application version in TestFlight and the App Store. The **Release Candidate** version does not have an expiration date.                                                                                                                                 |                                                                                                         |
 | **Release Type**     | Indicates the release type of your application. For example, if you have an application released to the market, you will see the type as **After Approval**.                                                                                                                        |                                                                                                         |
 | **Processing State** | This indicates the status of your application; it will appear as **`Valid`** when there are no issues. For instance, if your application has expired in the TestFlight environment, the state will be **`Expire`**. If the application is rejected, the state will be **`Reject`**. |                                                                                                         |

docs/publish-module/_category_.json

@@ -1,5 +1,5 @@
 {
-  "label": "Publish",
+  "label": "Publish to Stores",
   "position": 12,
   "collapsed": true,
   "collapsible": true,