update filename and fix acrolynx suggestions

Author: JamesBurnside

articles/communication-services/toc.yml

@@ -149,7 +149,7 @@ items:
       - name: 2. Request camera and microphone permissions
         href: tutorials/call-readiness/call-readiness-tutorial-part-2-requesting-device-access.md
       - name: 3. Microphone and camera setup before a call
-        href: tutorials/call-readiness/call-readiness-tutorial-part-3-camera-and-microphone-setup.md
+        href: tutorials/call-readiness/call-readiness-tutorial-part-3-camera-microphone-setup.md
   - name: Enable Push Notifications in your chat app
     href: tutorials/add-chat-push-notifications.md
 - name: Concepts

articles/communication-services/tutorials/call-readiness/call-readiness-overview.md

@@ -23,18 +23,18 @@ When a user intends to join a web call, their primary focus is on the conversati
 It may be impossible to predict every issue or combination of issues that may arise, but by applying this tutorial you can:
 
 - Reduce the likelihood of issues affecting a user during a call
-- Only expose an issue if it is going to negatively impact the experience
+- Only expose an issue if it's going to negatively impact the experience
 - Avoid making a user hunt for a resolution;  Offer guided help to resolve the issue
 
-Related to this tutorial is the Azure Communication Services [Network Testing Diagnostic Tool](../../concepts/developer-tools/network-diagnostic.md). This tool can be used by users for further troubleshooting in customer support scenarios.
+Related to this tutorial is the Azure Communication Services [Network Testing Diagnostic Tool](../../concepts/developer-tools/network-diagnostic.md). Users can user the Network Testing Diagnostics Tool for further troubleshooting in customer support scenarios.
 
 ## Tutorial Structure
 
 In this tutorial, we use the Azure Communication Services UI Library to create an experience that gets the user ready to join a call. This tutorial is structured into three parts:
 
 - Part 1: [Getting your user onto a supported browser](./call-readiness-tutorial-part-1-browser-support.md)
 - Part 2: [Ensuring your App has access to the microphone and camera](./call-readiness-tutorial-part-2-requesting-device-access.md)
-- Part 3: [Having your user select their desired microphone and camera](./call-readiness-tutorial-part-3-camera-and-microphone-setup.md)
+- Part 3: [Having your user select their desired microphone and camera](./call-readiness-tutorial-part-3-camera-microphone-setup.md)
 
 ## Prerequisites
 

articles/communication-services/tutorials/call-readiness/call-readiness-tutorial-part-1-browser-support.md

@@ -17,7 +17,7 @@ ms.subservice: calling
 
 [!INCLUDE [Public Preview Notice](../../includes/public-preview-include.md)]
 
-In this tutorial, we are using Azure Communication Services with the [UI Library](https://aka.ms/acsstorybook) to create an experience that gets users ready to join a call. The UI Library provides a set of rich components and UI controls that can be used to produce a Call Readiness experience, and a rich set of APIs to understand the user state.
+In this tutorial, we're using Azure Communication Services with the [UI Library](https://aka.ms/acsstorybook) to create an experience that gets users ready to join a call. The UI Library provides a set of rich components and UI controls that can be used to produce a Call Readiness experience, and a rich set of APIs to understand the user state.
 
 ## Prerequisites
 
@@ -138,7 +138,7 @@ export const checkEnvironmentSupport = async (callClient: StatefulCallClient): P
 }
 ```
 
-The data that returns from this call is the following:
+The data returned from `checkEnvironmentSupport` contains the following information:
 
 - Browser support
 - Browser version support
@@ -281,7 +281,7 @@ export const EnvironmentChecksComponent = (props: {
 
 We can then add the `EnvironmentChecksComponent` to the `App.tsx`. The App then move the user to the _Device Checks_ stage once the test is successful using the `onTestsSuccessful` callback:
 
-Let's now import the new component into our app in `App.tsx`
+Now we will import the new component into our app in `App.tsx`
 
 ```ts
 import { EnvironmentChecksComponent } from './EnvironmentChecksComponent';
@@ -314,7 +314,7 @@ const App = (): JSX.Element => {
 }
 ```
 
-You can now run the app. Try running on an [unsupported browser](../../concepts/voice-video-calling/calling-sdk-features.md#javascript-calling-sdk-support-by-os-and-browser) and you'll see the unsupported browser prompt:
+You can now run the app. Try running on an [unsupported browser](../../concepts/voice-video-calling/calling-sdk-features.md#javascript-calling-sdk-support-by-os-and-browser) and you see the unsupported browser prompt:
 
 ![Gif showing browser check failing](../media/call-readiness/browser-support-check-failed.gif)
 

articles/communication-services/tutorials/call-readiness/call-readiness-tutorial-part-2-requesting-device-access.md

@@ -111,7 +111,7 @@ export const requestCameraAndMicrophonePermissions = async (callClient: Stateful
 ### Prompting the user to grant access to the camera and microphone
 
 Now we have the prompts and check and request logic, we create a `DeviceAccessComponent` to prompt the user regarding device permissions.
-In this component we display different prompts to the user based on the device permission state:
+In this component, we display different prompts to the user based on the device permission state:
 
 - If the device permission state is unknown, we display a prompt to the user informing them we're checking for device permissions.
 - If we're requesting permissions, we display a prompt to the user encouraging them to accept the permissions request.
@@ -255,4 +255,4 @@ The app presents the user with prompts to guide them through device access:
 ## Next steps
 
 > [!div class="nextstepaction"]
-> [Part 3: Selecting a microphone and camera for the call](./call-readiness-tutorial-part-3-camera-and-microphone-setup.md)
+> [Part 3: Selecting a microphone and camera for the call](./call-readiness-tutorial-part-3-camera-microphone-setup.md)

articles/communication-services/tutorials/call-readiness/call-readiness-tutorial-part-3-camera-and-microphone-setup.md renamed to articles/communication-services/tutorials/call-readiness/call-readiness-tutorial-part-3-camera-microphone-setup.md

@@ -29,7 +29,7 @@ Access the full code for this tutorial on [GitHub](https://github.com/Azure-Samp
 ## Letting the user choose their camera, microphone and speaker
 
 From the previous two parts of the tutorial, the user is on a supported browser, and they have given us permission to access their camera and microphone. We can now make sure the user can choose the correct microphone, camera and speaker they want to use for their call.
-We present the user with a rich interface to choose their camera, microphone and speaker. Our final device setup UI will look like this:
+We present the user with a rich interface to choose their camera, microphone and speaker. Our final device setup UI looks like this:
 
 ![Image of the device setup page](../media/call-readiness/device-setup-page.png)