Fix PR issues

Author: luislera

hub/apps/publish/faq/troubleshoot-app-creation.md

@@ -22,4 +22,4 @@ If you encounter a permission error when you attempt to create a new app in Part
 
 ## Create a new Microsoft Entra ID tenant
 
-If the above steps do not resolve the error, create a new Microsoft Entra ID tenant and associate it with your Partner Center account. For more information, see [Associate existing Microsoft Entra ID with partner center](associate-azure-ad-with-partner-center.md).
+If the above steps do not resolve the error, create a new Microsoft Entra ID tenant and associate it with your Partner Center account. For more information, see [Associate existing Microsoft Entra ID with partner center](../partner-center/associate-existing-azure-ad-tenant-with-partner-center-account.md).

hub/apps/publish/publish-your-app/add-on/visibility-options.md

@@ -33,7 +33,7 @@ After your submission is published, the people in the group you specify will be
 
 If you plan to make the app available to a public audience at a certain date and time, you can select the box labeled **Make this product public on** when creating your submission. Enter the date and time (in UTC) when you’d like the product to become available to the public. Keep in mind the following:
 
-- The date and time that you select will apply to all markets. If you want to customize the release schedule for different markets, don’t use this box. Instead, create a new submission that changes your setting to **Public audience**, then use the [Schedule](./schedule-pricing-changes.md#configure-precise-release-scheduling) options to specify your release timing.
+- The date and time that you select will apply to all markets. If you want to customize the release schedule for different markets, don’t use this box. Instead, create a new submission that changes your setting to **Public audience**, then use the [Schedule](configure-release-schedule.md) options to specify your release timing.
 - Entering a date for **Make this product public on** does not apply to the Microsoft Store for Business and/or Microsoft Store for Education. To allow us to offer your app to these customers through organizational licensing, you’ll need to create a new submission with **Public audience** selected.
 - After the date and time that you select, all future submissions will use **Public audience**.
 
@@ -43,7 +43,7 @@ Here are some important things to keep in mind when choosing to distribute your
 
 - People in your private audience will be able to get the app by using a specific link to your app’s Store listing that requires them to sign in with their Microsoft account in order to view it. This link is provided when you select **Private audience**. You can also find it on your [App identity](../../view-app-identity-details.md) page under **URL if your app is only visible to certain people (requires authentication)**. Be sure to give your testers this link, not the regular URL to your Store listing.
 - Unless you choose an option in **Discoverability** that prevents it, people in your private audience will be able to find your app by searching within the Microsoft Store app. However, the web listing will not be discoverable via search, even to people in that audience.
-- You won’t be able to [configure release dates in the Schedule section](./configure-release-schedule.md#configure-precise-release-scheduling) of the **Pricing and availability page**, since your app won’t be released to customers outside of your private audience.
+- You won’t be able to [configure release dates in the Schedule section](configure-release-schedule.md) of the **Pricing and availability page**, since your app won’t be released to customers outside of your private audience.
 - Other selections you make will apply to people in this audience. For example, if you choose a price other than **Free**, people in your private audience will have to pay that price in order to acquire the app.
 - If you want to distribute different packages to different people in your private audience, after your initial submission you can use [package flights](../../package-flights.md) to distribute different package updates to subsets of your private audience. You can create additional known user groups to define who should get a specific package flight.
 - You can edit the membership of the known user group(s) in your private audience. However, keep in mind that if you remove someone who was in the group and previously downloaded your app, they will still be able to use the app, but they won’t get any updates that you provide (unless you choose **Public audience** at a later date).

hub/apps/publish/toc.yml

@@ -319,7 +319,7 @@ items:
             href: partner-center/remove-azure-ad-tenant-associations.md
       - name: Manage users, groups, and Microsoft Entra ID applications
         items: 
-          - name: Users, groups, and applications in Azure Active Directory
+          - name: Users, groups, and applications in Microsoft Entra ID
             href: partner-center/overview-users-groups-azure-ad-applications.md
           - name: Manage users in your Partner Center account
             href: partner-center/manage-users-in-partner-center.md