Skip to content

Commit 2dfa4f2

Browse files
fix image names
1 parent 452e2cb commit 2dfa4f2

File tree

6 files changed

+6
-6
lines changed

6 files changed

+6
-6
lines changed

articles/communication-services/tutorials/calling-widget/calling-widget-overview.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Creating a click to call experience with Azure Communication Services
2+
title: Get started with a click to call experience using Azure Communication Services
33
titleSuffix: An Azure Communication Services tutorial
44
description: Learn how to create a Calling Widget widget experience with the Azure Communication Services CallComposite to facilitate click to call.
55
author: dmceachern
@@ -12,11 +12,11 @@ ms.topic: tutorial
1212
ms.service: azure-communication-services
1313
ms.subservice: calling
1414
---
15-
# Creating a click to call experience with Azure Communication Services
15+
# Get started with a click to call experience using Azure Communication Services
1616

1717
[!INCLUDE [Public Preview Notice](../../includes/public-preview-include.md)]
1818

19-
![Home page of Calling Widget sample app](../media/calling-widget/sample-app-splash.png)
19+
![Home page of Calling Widget sample app](../media/calling-widget/sample-app-splash-widget-open.png)
2020

2121
This project aims to guide developers on creating a seamless click to call experience using the Azure Communication UI Library.
2222

articles/communication-services/tutorials/calling-widget/calling-widget-tutorial-part-1-creating-your-widget.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -441,11 +441,11 @@ import { CallingWidgetScreen } from './views/CallingWidgetScreen';
441441

442442
Once you have set the arguments defined in `App.tsx`, run the app with `npm run start` to see the changes:
443443

444-
![Screenshot of calling widget sample app home page widget closed](../media/calling-widget/sample-app-splash.png)
444+
![Screenshot of calling widget sample app home page widget closed](../media/calling-widget/sample-app-splash-widget-closed.png)
445445

446446
Then when you action the widget button, you should see:
447447

448-
![Screenshot of calling widget sample app home page widget open](../media/calling-widget/sample-app-widget-open.png)
448+
![Screenshot of calling widget sample app home page widget open](../media/calling-widget/sample-app-splash-widget-open.png)
449449

450450
Yay! We have made the control surface for the widget! Next, we'll discuss what we need to add to make this widget start a call in a new window.
451451

articles/communication-services/tutorials/calling-widget/calling-widget-tutorial-part-2-creating-new-window-experience.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -386,7 +386,7 @@ Now, when the application runs in a new window, it sees that it's supposed to st
386386

387387
Now when you pass in the arguments, set your `displayName`, and click `Start Call` you should see the following screens:
388388

389-
![Screenshot of click to call sample app home page with calling experience in new window](../media/calling-widget/calling-screen.png)
389+
![Screenshot of click to call sample app home page with calling experience in new window](../media/calling-widget/calling-screen-new-window.png)
390390

391391
With this new window experience, your users are able to:
392392
- continue using other tabs in their browser or other applications and still be able to see your call

0 commit comments

Comments
 (0)