NIT

Author: jiminwen-msft

articles/communication-services/quickstarts/chat/includes/chat-android.md

@@ -162,9 +162,9 @@ Copy the following code into class `MainActivity` in file `MainActivity.java`:
 > Initializing `ApplicationConstants` needs to be added to `MainActivity.java` if EITHER of the following conditions is met: 1. The push notification feature is NOT enabled. 2. The version for the Azure Communication Chat library for Android is < '2.0.0'. Otherwise, please refer to step 11 in [Android push notifications](../../../tutorials/chat-android-push-notification.md). Please refer to the sample APP of the SDK version that you are consuming for reference.
 
 `ACS_ENDPOINT`, `FIRST_USER_ID` and `FIRST_USER_ACCESS_TOKEN` are returned from calling Azure Function. Please check out [Azure Function integration](../../../tutorials/integrate-azure-function.md) for details. We use the response from calling Azure Function to initialize the list of parameters:
-1. `ACS_ENDPOINT`: the endpoint of your Communication Services resource.
-2. `FIRST_USER_ID` and `SECOND_USER_ID`: valid Communication Services user IDs generated by your Communication Services resource.
-3. `FIRST_USER_ACCESS_TOKEN`: the communication Services access token for `<FIRST_USER_ID>`.
+* `ACS_ENDPOINT`: the endpoint of your Communication Services resource.
+* `FIRST_USER_ID` and `SECOND_USER_ID`: valid Communication Services user IDs generated by your Communication Services resource.
+* `FIRST_USER_ACCESS_TOKEN`: the communication Services access token for `<FIRST_USER_ID>`.
 
 Code block for initialing application parameters by calling Azure Function: 
 ```java

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

@@ -195,28 +195,28 @@ Push notifications let clients be notified for incoming messages and other opera
 11. Add a custom `WorkManager` initializer by creating a class implementing `Configuration.Provider`:
 
 ```java
-public class MyAppConfiguration extends Application implements Configuration.Provider {
-    Consumer<Throwable> exceptionHandler = new Consumer<Throwable>() {
+    public class MyAppConfiguration extends Application implements Configuration.Provider {
+        Consumer<Throwable> exceptionHandler = new Consumer<Throwable>() {
+            @Override
+            public void accept(Throwable throwable) {
+                Log.i("YOUR_TAG", "Registration failed for push notifications!" + throwable.getMessage());
+            }
+        };
+    
         @Override
-        public void accept(Throwable throwable) {
-            Log.i("YOUR_TAG", "Registration failed for push notifications!" + throwable.getMessage());
+        public void onCreate() {
+            super.onCreate();
+            // Initialize application parameters here
+            WorkManager.initialize(getApplicationContext(), getWorkManagerConfiguration());
+        }
+    
+        @NonNull
+        @Override
+        public Configuration getWorkManagerConfiguration() {
+            return new Configuration.Builder().
+                setWorkerFactory(new RegistrationRenewalWorkerFactory(COMMUNICATION_TOKEN_CREDENTIAL, exceptionHandler)).build();
         }
-    };
-
-    @Override
-    public void onCreate() {
-        super.onCreate();
-        // Initialize application parameters here
-        WorkManager.initialize(getApplicationContext(), getWorkManagerConfiguration());
-    }
-
-    @NonNull
-    @Override
-    public Configuration getWorkManagerConfiguration() {
-        return new Configuration.Builder().
-            setWorkerFactory(new RegistrationRenewalWorkerFactory(COMMUNICATION_TOKEN_CREDENTIAL, exceptionHandler)).build();
     }
-}
 ```
 **Explanation to code above:** The default initializer of `WorkManager` has been disabled in step 9. This step implements `Configuration.Provider` to provide a customized 'WorkFactory', which is responsible to create `WorkerManager` during runtime. 
 

articles/communication-services/tutorials/integrate-azure-function.md

@@ -31,28 +31,28 @@ Before you get started, make sure to:
 ```
 4. Modify the `index.js` file so it looks like the code below:
 ```JavaScript
-const { CommunicationIdentityClient } = require('@azure/communication-identity');
-const connectionString = '<your_connection_string>'
-const acsEndpoint = "<your_ACS_endpoint>"
-
-module.exports = async function (context, req) {
-    let tokenClient = new CommunicationIdentityClient(connectionString);
-
-    const userIDHolder = await tokenClient.createUser();
-    const userId = userIDHolder.communicationUserId
-
-    const userToken = await (await tokenClient.getToken(userIDHolder, ["chat"])).token;
-
-    context.res = {
-        body: {
-            acsEndpoint,
-            userId,
-            userToken
-        }
-    };
-}
+    const { CommunicationIdentityClient } = require('@azure/communication-identity');
+    const connectionString = '<your_connection_string>'
+    const acsEndpoint = "<your_ACS_endpoint>"
+    
+    module.exports = async function (context, req) {
+        let tokenClient = new CommunicationIdentityClient(connectionString);
+    
+        const userIDHolder = await tokenClient.createUser();
+        const userId = userIDHolder.communicationUserId
+    
+        const userToken = await (await tokenClient.getToken(userIDHolder, ["chat"])).token;
+    
+        context.res = {
+            body: {
+                acsEndpoint,
+                userId,
+                userToken
+            }
+        };
+    }
 ```
-**Explanation to code above**: The first line import the interface for the `CommunicationIdentityClient`. The connection string in the second line can be found in your ACS resource in the Azure Portal. The `ACSEndpoint` is the URL of the ACS resource that was created. 
+**Explanation to code above**: The first line import the interface for the `CommunicationIdentityClient`. The connection string in the second line can be found in your ACS resource in the Azure portal. The `ACSEndpoint` is the URL of the ACS resource that was created. 
 
 5. Open the local Azure Function folder in Visual Studio Code. Open the `index.js` and run the local Azure Function. A local Azure Function endpoint will be created and printed in the terminal. The printed message looks similar to:
 
@@ -63,16 +63,16 @@ HttpTrigger1: [GET,POST] http://localhost:7071/api/HttpTrigger1
 
 Open the link in a browser. The result will be similar to this example:
 ```
-{
-  "acsEndpoint": "<Azure Function endpoint>",
-  "userId": "8:acs:a636364c-c565-435d-9818-95247f8a1471_00000014-f43f-b90f-9f3b-8e3a0d00c5d9",
-  "userToken": "eyJhbGciOiJSUzI1NiIsImtpZCI6IjEwNiIsIng1dCI6Im9QMWFxQnlfR3hZU3pSaXhuQ25zdE5PU2p2cyIsInR5cCI6IkpXVCJ9.eyJza3lwZWlkIjoiYWNzOmE2MzYzNjRjLWM1NjUtNDM1ZC05ODE4LTk1MjQ3ZjhhMTQ3MV8wMDAwMDAxNC1mNDNmLWI5MGYtOWYzYi04ZTNhMGQwMGM1ZDkiLCJzY3AiOjE3OTIsImNzaSI6IjE2Njc4NjI3NjIiLCJleHAiOjE2Njc5NDkxNjIsImFjc1Njb3BlIjoiY2hhdCIsInJlc291cmNlSWQiOiJhNjM2MzY0Yy1jNTY1LTQzNWQtOTgxOC05NTI0N2Y4YTE0NzEiLCJyZXNvdXJjZUxvY2F0aW9uIjoidW5pdGVkc3RhdGVzIiwiaWF0IjoxNjY3ODYyNzYyfQ.t-WpaUUmLJaD0V2vgn3M5EKdJUQ_JnR2jnBUZq3J0zMADTnFss6TNHMIQ-Zvsumwy14T1rpw-1FMjR-zz2icxo_mcTEM6hG77gHzEgMR4ClGuE1uRN7O4-326ql5MDixczFeIvIG8s9kAeJQl8N9YjulvRkGS_JZaqMs2T8Mu7qzdIOiXxxlmcl0HeplxLaW59ICF_M4VPgUYFb4PWMRqLXWjKyQ_WhiaDC3FvhpE_Bdb5U1eQXDw793V1_CRyx9jMuOB8Ao7DzqLBQEhgNN3A9jfEvIE3gdwafpBWlQEdw-Uuf2p1_xzvr0Akf3ziWUsVXb9pxNlQQCc19ztl3MIQ"
-}
+    {
+      "acsEndpoint": "<Azure Function endpoint>",
+      "userId": "8:acs:a636364c-c565-435d-9818-95247f8a1471_00000014-f43f-b90f-9f3b-8e3a0d00c5d9",
+      "userToken": "eyJhbGciOiJSUzI1NiIsImtpZCI6IjEwNiIsIng1dCI6Im9QMWFxQnlfR3hZU3pSaXhuQ25zdE5PU2p2cyIsInR5cCI6IkpXVCJ9.eyJza3lwZWlkIjoiYWNzOmE2MzYzNjRjLWM1NjUtNDM1ZC05ODE4LTk1MjQ3ZjhhMTQ3MV8wMDAwMDAxNC1mNDNmLWI5MGYtOWYzYi04ZTNhMGQwMGM1ZDkiLCJzY3AiOjE3OTIsImNzaSI6IjE2Njc4NjI3NjIiLCJleHAiOjE2Njc5NDkxNjIsImFjc1Njb3BlIjoiY2hhdCIsInJlc291cmNlSWQiOiJhNjM2MzY0Yy1jNTY1LTQzNWQtOTgxOC05NTI0N2Y4YTE0NzEiLCJyZXNvdXJjZUxvY2F0aW9uIjoidW5pdGVkc3RhdGVzIiwiaWF0IjoxNjY3ODYyNzYyfQ.t-WpaUUmLJaD0V2vgn3M5EKdJUQ_JnR2jnBUZq3J0zMADTnFss6TNHMIQ-Zvsumwy14T1rpw-1FMjR-zz2icxo_mcTEM6hG77gHzEgMR4ClGuE1uRN7O4-326ql5MDixczFeIvIG8s9kAeJQl8N9YjulvRkGS_JZaqMs2T8Mu7qzdIOiXxxlmcl0HeplxLaW59ICF_M4VPgUYFb4PWMRqLXWjKyQ_WhiaDC3FvhpE_Bdb5U1eQXDw793V1_CRyx9jMuOB8Ao7DzqLBQEhgNN3A9jfEvIE3gdwafpBWlQEdw-Uuf2p1_xzvr0Akf3ziWUsVXb9pxNlQQCc19ztl3MIQ"
+    }
 ```
 
 6. Deploy the local function to the cloud. More details can be found in [this documentation](../../azure-functions/functions-develop-vs-code.md).
 
-7. **Test the deployed Azure Function.** First, find your Azure Function in the Azure Portal. Then, use the "Get Function URL" button to get the Azure Function endpoint. The result you see should be similar to what was shown in step 5. The Azure Function endpoint will be used in the app for initializing application parameters.
+7. **Test the deployed Azure Function.** First, find your Azure Function in the Azure portal. Then, use the "Get Function URL" button to get the Azure Function endpoint. The result you see should be similar to what was shown in step 5. The Azure Function endpoint will be used in the app for initializing application parameters.
 
 8. Implement `UserTokenClient`, which is used to call the target Azure Function resource and obtain the ACS endpoint, user ID and user token from the returned JSON object. Refer to the sample app for usage.
 
@@ -83,7 +83,7 @@ Open the link in a browser. The result will be similar to this example:
 ## (Optional) secure the Azure Function endpoint
 For demonstration purposes, this sample uses a publicly accessible endpoint by default to fetch an Azure Communication Services token. For production scenarios, one option is to use your own secured endpoint to provision your own tokens.
 
-With extra configuration, this sample supports connecting to an Azure Active Directory (Azure AD) protected endpoint so that user log in is required for the app to fetch an Azure Communication Services token. The user will be required to sign in with Microsoft account to access the app. This setup increases the security level while users are required to log in. Decide whether to enable it based on the use cases.
+With extra configuration, this sample supports connecting to an Azure Active Directory (Azure AD) protected endpoint so that user log is required for the app to fetch an Azure Communication Services token. The user will be required to sign in with Microsoft account to access the app. This setup increases the security level while users are required to log in. Decide whether to enable it based on the use cases.
 
 Note that we currently don't support Azure AD in sample code. Follow the links below to enable it in your app and Azure Function: