From af933d6165542d4e692d7da815193d8f0d5e0102 Mon Sep 17 00:00:00 2001 From: Muindi Stephen <57146128+MuindiStephen@users.noreply.github.com> Date: Mon, 16 Mar 2026 22:53:12 +0300 Subject: [PATCH] Update README.md: Added some spacing to step 7 description --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 527809c..808df3e 100644 --- a/README.md +++ b/README.md @@ -161,7 +161,7 @@ Leave the dialog text field empty and press the call button to start a call. You ### 7. Create a Push Credential using your FCM Server Key -You will need to store the FCM Server key(The **Server key** of your project from the Firebase console, found under Settings/Cloud messaging) with Twilio so that we can send push notifications to your app on your behalf. Once you store the Server key with Twilio, it will get assigned a Push Credential SID so that you can later specify which key we should use to send push notifications. +You will need to store the FCM Server key (The **Server key** of your project from the Firebase console, found under Settings/Cloud messaging) with Twilio so that we can send push notifications to your app on your behalf. Once you store the Server key with Twilio, it will get assigned a Push Credential SID so that you can later specify which key we should use to send push notifications. A FCMv1 server key can be generated from a Firebase Service account by selecting `Create New Key` and subsequently selecting a 'JSON' key type. Keep track of this generated key due to its limited accessibility. For more information on how to create a FCMv1 token, please follow this [document](https://help.twilio.com/articles/20768292997147-Updating-Twilio-Push-for-FCM-HTTP-v1-API).