Fixed the errors

foundation-extensions/adobe-experience-platform-assurance/assurance-sdk-error-logs.md

@@ -61,7 +61,7 @@ func application(_ application: UIApplication, didFinishLaunchingWithOptions lau
 
 ### Copy link or open QR code from Project Griffon
 
-The PIN screen may not show if the link or QR code is incorrect (or doesn't contain the query parameter `adb_validation_sessionid`. You may detect this error by seeing console logs with the following strings:
+The PIN screen may not show if the link or QR code is incorrect (or doesn't contain the query parameter `adb_validation_sessionid`). You may detect this error by seeing console logs with the following strings:
 
 {% tabs %}
 {% tab title="Android" %}

foundation-extensions/mobile-core/identity/identity-api-reference.md

@@ -15,7 +15,7 @@ If the provided URL is null or empty, it is returned as is. Otherwise, the follo
   * `TS` - A timestamp taken when this request was made
 * The optional `adobe_aa_vid` attribute is the URL-encoded Analytics Custom Visitor ID (VID), if previously set in the [Analytics extension](https://aep-sdks.gitbook.io/docs/using-mobile-extensions/adobe-analytics).
 
-When [AdobeCallbackWithError](https://aep-sdks.gitbook.io/docs/using-mobile-extensions/mobile-core/mobile-core-api-reference#adobecallbackwitherror) is provided, and you are fetching the attributes from the Mobile SDK, the timeout value is 500ms. If the operation times out or an unexpected error occurs, the `fail` method is called with the appropriate \[AdobeError\][https://aep-sdks.gitbook.io/docs/using-mobile-extensions/mobile-core/mobile-core-api-reference\#adobeerror](https://aep-sdks.gitbook.io/docs/using-mobile-extensions/mobile-core/mobile-core-api-reference#adobeerror)).
+When [AdobeCallbackWithError](https://aep-sdks.gitbook.io/docs/using-mobile-extensions/mobile-core/mobile-core-api-reference#adobecallbackwitherror) is provided, and you are fetching the attributes from the Mobile SDK, the timeout value is 500ms. If the operation times out or an unexpected error occurs, the `fail` method is called with the appropriate [AdobeError]((https://aep-sdks.gitbook.io/docs/using-mobile-extensions/mobile-core/mobile-core-api-reference#adobeerror).).
 
 #### Java
 
@@ -660,7 +660,7 @@ string identityVersion = ACPIdentity.ExtensionVersion();
 
 This API retrieves the ECID that was generated when the app was initially launched and is stored in the ECID Service.
 
-This ID is preserved between app upgrades, is saved and restored during the standard application backup process, and is removed at uninstall. The values are returned via the \[AdobeCallback\][https://aep-sdks.gitbook.io/docs/using-mobile-extensions/mobile-core/mobile-core-api-reference\#adobecallback](https://aep-sdks.gitbook.io/docs/using-mobile-extensions/mobile-core/mobile-core-api-reference#adobecallback)).
+This ID is preserved between app upgrades, is saved and restored during the standard application backup process, and is removed at uninstall. The values are returned via the [AdobeCallback](https://aep-sdks.gitbook.io/docs/using-mobile-extensions/mobile-core/mobile-core-api-reference#adobecallback).
 
 When [AdobeCallbackWithError](https://aep-sdks.gitbook.io/docs/using-mobile-extensions/mobile-core/mobile-core-api-reference#adobecallbackwitherror) is provided, and you are fetching the ECID from the Mobile SDK, the timeout value is 500ms. If the operation times out or an unexpected error occurs, the `fail` method is called with the appropriate [AdobeError](https://aep-sdks.gitbook.io/docs/using-mobile-extensions/mobile-core/mobile-core-api-reference#adobeerror).
 

getting-started/get-the-sdk.md

@@ -658,7 +658,7 @@ To enable these permissions, add the following lines to your `AndroidManifest.xm
 <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
 ```
 
-## Watch the Vvdeo
+## Watch the Video
 
 {% embed url="https://www.youtube.com/watch?v=K99NwR6Y08E" caption="Video: How to use Cocoapods and Gradle with SDK extensions & dependencies" %}
 

resources/adobe-experience-platform-mini-programs-sdk/README.md

@@ -31,7 +31,7 @@ At this time, Experience Cloud ID (ECID or MCID) **are not** supported.
 {% endhint %}
 
 {% hint style="info" %}
-To learn more about Analytics Visitor ID, see the [Adobe Analytics implementation guide](https://experienceleague.adobe.com/docs/analytics/implementation/js/xdevice-visid/xdevice-connecting.html?lang=en).
+To learn more about Analytics Visitor ID, see the [Adobe Analytics implementation guide](https://experienceleague.adobe.com/docs/analytics/components/cda/overview.html?lang=en).
 {% endhint %}
 
 ### **Licensing**
@@ -57,7 +57,7 @@ The SDK is available as read-only open source and is distributed with an Apache
 * 从服务器端获取或者小程序端自动生成
 
 {% hint style="info" %}
-有关Analytics Visitor ID的信息，请参阅 [Adobe Analytics implementation guide](https://experienceleague.adobe.com/docs/analytics/implementation/js/xdevice-visid/xdevice-connecting.html?lang=en)
+有关Analytics Visitor ID的信息，请参阅 [Adobe Analytics implementation guide](https://experienceleague.adobe.com/docs/analytics/components/cda/overview.html?lang=en)
 {% endhint %}
 
 ### 文档与授权

resources/building-mobile-extensions/building-an-extension.md

@@ -246,7 +246,7 @@ Some registration errors, such as undefined names, name conflicts, or type check
 
 #### Unregistering your extension
 
-If your extension does not need to be active at all times, you can unregister your extension by using `unregisterExtension` from the `ACPExtensionApi` (iOS / `ExtensionApi` (Android). This process allows you to have more granular resource control, but the listeners that you registered will be unregistered. If you overrode `onUnregister`, you should see a call into your implementation that allows you to clean up resources before the instance is released.
+If your extension does not need to be active at all times, you can unregister your extension by using `unregisterExtension` from the `ACPExtensionApi` (iOS) / `ExtensionApi` (Android). This process allows you to have more granular resource control, but the listeners that you registered will be unregistered. If you overrode `onUnregister`, you should see a call into your implementation that allows you to clean up resources before the instance is released.
 
 {% hint style="info" %}
 

resources/building-mobile-extensions/building-the-launch-extension-interface.md

@@ -8,7 +8,7 @@
 
 2. (Optional) Create a new listing in the Exchange Partner Portal.
 
-   For more information, see the document on \[creating an exchange listing\]([https://experienceleague.adobe.com/docs/launch/using/extension-dev/submit/create-listing.html](https://experienceleague.adobe.com/docs/launch/using/extension-dev/submit/create-listing.html).
+   For more information, see the document on [creating an exchange listing](https://experienceleague.adobe.com/docs/launch/using/extension-dev/submit/create-listing.html).
 
 3. Create a new Adobe I/O integration.
 

resources/troubleshooting-guides/troubleshooting-push.md

@@ -6,10 +6,10 @@ This troubleshooting guide requires [Project Griffon](../../beta/project-griffon
 
 When implementing push messaging via the Adobe Experience Platform Mobile SDK, you can validate the client-side implementation by verifying that you completed the following steps:
 
-1. [Pass the device's push token to the SDK](troubleshooting-push.md#pass-the-push-identifier-to-the-sdk).
-2. [Verify push token sync with the Experience Cloud Identity service](troubleshooting-push.md#validate-setpushidentifier-event).
-3. [Ensure user opt in for push in Adobe Analytics](troubleshooting-push.md#validate-analytics-request-with-push-optin).
-4. [Confirm user ID is correctly set (and is same from steps 2 and 3, above](troubleshooting-push.md#validate-the-user-id-is-correct)).
+1. [Pass the device's push token to the SDK](#pass-the-push-identifier-to-the-sdk).
+2. [Verify push token sync with the Experience Cloud Identity service](#validate-push-token-sync-with-the-experience-cloud-identity-service).
+3. [Ensure user opt in for push in Adobe Analytics](#ensure-user-opt-in-for-push-in-adobe-analytics).
+4. [Confirm user ID is correctly set (and is same from steps 2 and 3, above](#confirm-that-the-user-id-is-correctly-set).
 
 ## Pass the Push Identifier to the SDK
 

resources/user-guides/getting-started-with-adobe-experience-platform/README.md

@@ -94,7 +94,7 @@ Set the `LAUNCH_ENVIRONMENT_FILE_ID` to the copied Environment File ID in the `M
 
 This application uses the Adobe Experience Platform Edge extension for sending XDM formatted data to the Adobe Experience Edge Network and so to Adobe Experience Platform. The XDM data is modelled based on the XDM Schemas you have configured in Adobe Experience Platform.
 
-The sample app includes automatically generated source classes for the XDM Objects that define the commerce field group configured in the previous step. To explore these, check the `MobileSDKCommerceSchema` class and its usages in `EdgeViewController.swift` (iOS) / `EdgeTab.java` (Android\`.
+The sample app includes automatically generated source classes for the XDM Objects that define the commerce field group configured in the previous step. To explore these, check the `MobileSDKCommerceSchema` class and its usages in `EdgeViewController.swift` (iOS) / `EdgeTab.java` (Android)`.
 
 ### Commerce events <a id="commerce-events"></a>
 

tutorials/end2end/audience-manager.md

@@ -77,7 +77,7 @@ A configuration in the Adobe Analytics Admin Console is required to start forwar
 
 >[!NOTE] Since SSF needs to be enabled per report suite, don't forget to repeat this step for your real report suites when you are deploying SSF on your actual site's report suite.
 >
->Also, if the SSF option is grayed out, you will need to "map the report suite(s) to your Experience Cloud Org in order to enable the option. This is explained in [the documentation](https://experienceleague.adobe.com/docs/analytics/admin/admin-tools/server-side-forwarding/ssf.html?lang=en).
+>Also, if the SSF option is grayed out, you will need to map the report suite(s) to your Experience Cloud Org in order to enable the option. This is explained in [the documentation](https://experienceleague.adobe.com/docs/analytics/admin/admin-tools/server-side-forwarding/ssf.html?lang=en).
 
 Once this step has been completed, and if you have the Experience Cloud ID Service enabled, data will be forwarded from Analytics to AAM. However, to complete the process so that the response comes back correctly from AAM to the page (and also to Analytics via the Audience Analytics feature), you must complete the following step in Launch as well. Don't worry, it's super easy.