Skip to content

Commit bf4f47f

Browse files
committed
Fix score on overview section
1 parent 7da54ae commit bf4f47f

File tree

1 file changed

+13
-12
lines changed

1 file changed

+13
-12
lines changed

articles/communication-services/how-tos/calling-sdk/includes/manage-video/manage-video-windows.md

Lines changed: 13 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -9,16 +9,17 @@ ms.author: rifox
99

1010
### Request access to the microphone
1111

12-
The app will require access to the camera to run properly. In UWP apps, the camera capability should be declared in the app manifest file.
13-
he following steps exemplify how to achieve that.
12+
The app requires access to the camera to run properly. In UWP apps, the camera capability should be declared in the app manifest file.
13+
14+
The following steps exemplify how to achieve that.
1415

1516
1. In the `Solution Explorer` panel, double click on the file with `.appxmanifest` extension.
1617
2. Click on the `Capabilities` tab.
1718
3. Select the `Camera` check box from the capabilities list.
1819

1920
### Create UI buttons to place and hang up the call
2021

21-
This simple sample app will contain two buttons. One for placing the call and another to hang up a placed call.
22+
This simple sample app contains two buttons. One for placing the call and another to hang up a placed call.
2223
The following steps exemplify how to add these buttons to the app.
2324

2425
1. In the `Solution Explorer` panel, double click on the file named `MainPage.xaml` for UWP, or `MainWindows.xaml` for WinUI 3.
@@ -46,14 +47,14 @@ using Azure.Communication;
4647
using Azure.Communication.Calling;
4748
```
4849

49-
Please keep `MainPage.xaml.cs` or `MainWindows.xaml.cs` open. The next steps will add more code to it.
50+
Keep `MainPage.xaml.cs` or `MainWindows.xaml.cs` open. The next steps will add more code to it.
5051

5152
## Allow app interactions
5253

5354
The UI buttons previously added need to operate on top of a placed `Call`. It means that a `Call` data member should be added to the `MainPage` or `MainWindow` class.
5455
Additionally, to allow the asynchronous operation creating `CallAgent` to succeed, a `CallAgent` data member should also be added to the same class.
5556

56-
Please add the following data members to the `MainPage` or `MainWindow` class:
57+
Add the following data members to the `MainPage` or `MainWindow` class:
5758
```csharp
5859
CallAgent callAgent;
5960
Call call;
@@ -91,8 +92,8 @@ The following classes and interfaces handle some of the major features of the Az
9192

9293
## Register video handler
9394

94-
A UI component, like XAML's MediaElement or MediaPlayerElement, will require the app registering a configuration for rendering local and remote video feeds.
95-
Please add the following content between the `Package` tags of the `Package.appxmanifest`:
95+
A UI component, like XAML's MediaElement or MediaPlayerElement, you need the app registering a configuration for rendering local and remote video feeds.
96+
Add the following content between the `Package` tags of the `Package.appxmanifest`:
9697

9798
```xml
9899
<Extensions>
@@ -107,7 +108,7 @@ Please add the following content between the `Package` tags of the `Package.appx
107108

108109
## Initialize the CallAgent
109110

110-
To create a `CallAgent` instance from `CallClient` you must use `CallClient.CreateCallAgent` method that asynchronously returns a `CallAgent` object once it is initialized.
111+
To create a `CallAgent` instance from `CallClient`, you must use `CallClient.CreateCallAgent` method that asynchronously returns a `CallAgent` object once it's initialized.
111112

112113
To create `CallAgent`, you must pass a `CommunicationTokenCredential` object and a `CallAgentOptions` object. Keep in mind that `CommunicationTokenCredential` throws if a malformed token is passed.
113114

@@ -128,11 +129,11 @@ this.callAgent.OnCallsUpdated += Agent_OnCallsUpdatedAsync;
128129
this.callAgent.OnIncomingCall += Agent_OnIncomingCallAsync;
129130
```
130131

131-
`<AUTHENTICATION_TOKEN>` must be replaced by a valid credential token for your resource. Refer to the [user access token](../../../../quickstarts/identity/access-tokens.md) documentation if a credential token has to be sourced.
132+
Change the `<AUTHENTICATION_TOKEN>` with a valid credential token for your resource. Refer to the [user access token](../../../../quickstarts/identity/access-tokens.md) documentation if a credential token has to be sourced.
132133

133134
## Place a 1:1 call with video camera
134135

135-
The objects needed for creating a `CallAgent` are now ready. It is time to asynchronously create `CallAgent` and place a video call.
136+
The objects needed for creating a `CallAgent` are now ready. It's time to asynchronously create `CallAgent` and place a video call.
136137

137138
The following code should be added after handling the exception from the previous step.
138139

@@ -282,6 +283,6 @@ await this.call.HangUpAsync(new HangUpOptions());
282283

283284
## Run the code
284285

285-
Make sure Visual Studio will build the app for `x64`, `x86` or `ARM64`, then hit `F5` to start running the app. After that, click on the `Call` button to place a call to the callee defined.
286+
Make sure Visual Studio builds the app for `x64`, `x86` or `ARM64`, then hit `F5` to start running the app. After that, click on the `Call` button to place a call to the callee defined.
286287

287-
Keep in mind that the first time the app runs, the system will prompt user for granting access to the microphone.
288+
Keep in mind that the first time the app runs, the system prompts user for granting access to the microphone.

0 commit comments

Comments
 (0)