Removed blockers

Fixed blocking issues

Author: vac0224

articles/communication-services/how-tos/calling-sdk/push-notifications.md

@@ -67,5 +67,5 @@ In case that you want to revoke an identity you need to follow [this process](..
 
 ## Related topics
 
-- [Migrate Android SDK push notifications to FCM v1](../../tutorials/call-chat-migrate-android-push-fcmv1.md)
-- [Register for Android SDK push notifications using FCM v1](../../tutorials/call-chat-register-android-push-fcmv1.md)
+- [Migrate Android SDK push notifications to FCM v1](../../tutorials/call-chat-migrate-android-push-fcm-v1.md)
+- [Register for Android SDK push notifications using FCM v1](../../tutorials/call-chat-register-android-push-fcm-v1.md)

articles/communication-services/toc.yml

@@ -242,9 +242,9 @@ items:
     - name: Send short URL
       href: tutorials/sms-url-shortener.md
     - name: Migrate to Android push notifications FCM v1
-      href: tutorials/call-chat-migrate-android-push-fcmv1.md
+      href: tutorials/call-chat-migrate-android-push-fcm-v1.md
     - name: Register for Android push notifications FCM v1
-      href: tutorials/call-chat-register-android-push-fcmv1.md
+      href: tutorials/call-chat-register-android-push-fcm-v1.md
     - name: Phone numbers
       items:
       - name: Port a phone number into Azure

articles/communication-services/tutorials/call-chat-migrate-android-push-fcmv1.md renamed to articles/communication-services/tutorials/call-chat-migrate-android-push-fcm-v1.md

@@ -16,7 +16,7 @@ This article applies to call and chat applications using Android SDK with Fireba
 
 On June 20, 2023, Google announced that it [deprecated sending messages using the FCM legacy APIs](https://firebase.google.com/docs/cloud-messaging). Google is removing the legacy FCM from service in June 2024. Google recommends [migrating from legacy FCM APIs to FCM HTTP v1](https://firebase.google.com/docs/cloud-messaging/migrate-v1).
 
-If you have a new Android application or never used Google FCM, see the [Register for Android SDK push notifications using FCM v1](./call-chat-register-android-push-fcmv1.md) article.
+If you have a new Android application or never used Google FCM, see the [Register for Android SDK push notifications using FCM v1](./call-chat-register-android-push-fcm-v1.md) article.
 
 If your Android application uses the push notification feature, complete the following steps to migrate your push notification to FCM HTTP v1.
 
@@ -30,7 +30,7 @@ If your Android application uses the push notification feature, complete the fol
 
 4. Click **Generate new private key** to download a JSON file containing your new private key.
 
-    ![Generate new private key for FMC v1 in Firebase console.](./media/call-chat-fcm-firebase-console-gen-key.png)
+    ![Screenshot of how to generate new private key for FMC v1 in Firebase console.](./media/call-chat-fcm-firebase-console-gen-key.png)
 
 5. Find and open the downloaded JSON file. You need values from this file for the next step.
 
@@ -42,7 +42,8 @@ If your Android application uses the push notification feature, complete the fol
 2. Open **Settings** > **Google (FCM v1)**.
 
 3. Enter the values from your downloaded JSON file in the text boxes for **Private Key**, **Client Email**, and **Project ID**.
-    ![Provide new private key credentials for FCM v1 in Azure portal settings.](./media/call-chat-fcmv1-credentials-add.png)
+    
+    ![Screenshot of how to provide a new private key credentials for FCM v1 in Azure portal settings.](./media/call-chat-fcmv1-credentials-add.png)
 
 4. Click **Save**.
 
@@ -53,7 +54,8 @@ If your Android application uses the push notification feature, complete the fol
 2. Open **Settings** > **Google (GCM/FCM)**.
 
 3. Clear the **API Key** text box.
-        ![Remove legacy credentials for GCM / FCM from Azure portal settings.](./media/call-chat-fcm-credentials-remove.png)
+    
+    ![Screenshot of how to remove legacy credentials for GCM / FCM from Azure portal settings.](./media/call-chat-fcm-credentials-remove.png)
 
 4. Click **Save**.
 

articles/communication-services/tutorials/call-chat-register-android-push-fcmv1.md renamed to articles/communication-services/tutorials/call-chat-register-android-push-fcm-v1.md

@@ -16,7 +16,7 @@ This article applies to call and chat applications using Android SDK with Fireba
 
 On June 20, 2023, Google announced that it [deprecated sending messages using the FCM legacy APIs](https://firebase.google.com/docs/cloud-messaging). Google is removing the legacy FCM from service in June 2024. Google recommends [migrating from legacy FCM APIs to FCM HTTP v1](https://firebase.google.com/docs/cloud-messaging/migrate-v1).
 
-If your existing Android application uses the push notification feature, you need to [migrate to the FCM HTTP v1 endpoint](./call-chat-migrate-android-push-fcmv1.md).
+If your existing Android application uses the push notification feature, you need to [migrate to the FCM HTTP v1 endpoint](./call-chat-migrate-android-push-fcm-v1.md).
 
 If you have a new Android application or never used Google FCM, complete the following steps to register for Android SDK push notification using FCM HTTP v1.
 
@@ -31,8 +31,8 @@ Complete the following steps to migrate your push notification to FCM HTTP v1.
 3. Select any programming language.
 
 4. Click **Generate new private key** to download a JSON file containing your new private key.
-
-    ![Generate new private key for FMC v1 in Firebase console.](./media/call-chat-fcm-firebase-console-gen-key.png)
+    
+    ![Screenshot of how to generate a new private key for FMC v1 in Firebase console.](./media/call-chat-fcm-firebase-console-gen-key.png)
 
 5. Find and open the downloaded JSON file. You need values from this file for the next step.
 
@@ -44,7 +44,8 @@ Complete the following steps to migrate your push notification to FCM HTTP v1.
 2. Open **Settings** > **Google (FCM v1)**.
 
 3. Enter the values from your downloaded JSON file in the text boxes for **Private Key**, **Client Email**, and **Project ID**.
-    ![Provide new private key credentials for FCM v1 in Azure portal settings.](./media/call-chat-fcmv1-credentials-add.png)
+    
+    ![Screenshot of how to provide a new private key credentials for FCM v1 in Azure portal settings.](./media/call-chat-fcmv1-credentials-add.png)
 
 4. Click **Save**.
 

articles/communication-services/tutorials/chat-android-push-notification.md

@@ -238,5 +238,5 @@ If the app is integrated with Azure Function, initialization of application para
 
 ## Related topics
 
-- [Migrate Android SDK push notifications to FCM v1](./call-chat-migrate-android-push-fcmv1.md)
-- [Register for Android SDK push notifications using FCM v1](./call-chat-register-android-push-fcmv1.md)
+- [Migrate Android SDK push notifications to FCM v1](./call-chat-migrate-android-push-fcm-v1.md)
+- [Register for Android SDK push notifications using FCM v1](./call-chat-register-android-push-fcm-v1.md)