Skip to content

Commit 4f60dd1

Browse files
committed
removed space & h2
1 parent f54b053 commit 4f60dd1

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/communication-services/concepts/analytics/recording-logs.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ Recording file is generated at the end of a call or meeting. The recording can b
4343
|recordingEndReason| String | The reason why the recording ended |
4444

4545

46-
### Call recording and sample data
46+
## Call recording and sample data
4747
```json
4848
"operationName": "Call Recording Summary",
4949
"operationVersion": "1.0",
@@ -55,7 +55,7 @@ A call can have one recording or many recordings depending on how many times a r
5555
For example, if an agent initiates an outbound call in a recorded line and the call drops due to poor network signal, the `callid` will have one `recordingid`. If the agent calls back the customer, the system will generate a new `callid` as well as a new `recordingid`.
5656

5757

58-
#### Example1: Call recording for " One call to one recording"
58+
#### Example1: Call recording for "One call to one recording"
5959
```json
6060
"properties"
6161
{
@@ -79,7 +79,7 @@ For example, if an agent initiates an outbound call in a recorded line and the c
7979

8080
If the agent initiated a recording and stopped and restarted the recording multiple times while the call is still on, the `callid` will have many `recordingid` depending on how many times the recording events were triggered.
8181

82-
#### Example2: Call recording for " One call to many recordings"
82+
#### Example2: Call recording for "One call to many recordings"
8383
```json
8484

8585
{

0 commit comments

Comments
 (0)