Skip to content

Commit b16a5d1

Browse files
committed
Apply PR suggestions
1 parent d6ba639 commit b16a5d1

1 file changed

Lines changed: 9 additions & 9 deletions

File tree

docs/DEBUGGING.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ To break into the debugger for a specific element:
2525
2. In the Elements pane, click on the element to break into
2626
3. Switch to Console pane, type `$0.webChat.debugger`
2727

28-
Then, it should break into the debugger.
28+
Then it should break into the debugger.
2929

3030
![Screenshot of DevTools debugger breaking into the root container component](media/DEBUGGING/devtools-debugger.png)
3131

@@ -35,28 +35,28 @@ Use DevTools Console `debug()` to attach a debugger to specific breakpoint funct
3535

3636
| Component | Breakpoint | Arguments | Description |
3737
| -------------- | ------------------ | ------------------------ | ------------------------ |
38-
| Root container | `incomingActivity` | `{ activity: Activity }` | When an activity arrive |
38+
| Root container | `incomingActivity` | `{ activity: Activity }` | When an activity arrives |
3939
| Activity | `render` | | When the activity render |
4040

4141
To break into the debugger when an activity arrives:
4242

4343
1. Press <kbd>F12</kbd> to open Chrome DevTools
4444
2. In the Elements pane, click on the Web Chat root container to break into
4545
- Or type `inspect($('.webchat'))` to select the first root container on the page
46-
3. Switch to Console pane, type `debug($0.webChat.breakpoint.incomingActivity)`
46+
3. Switch to the Console pane, type `debug($0.webChat.breakpoint.incomingActivity)`
4747

48-
When an activity arrive, it will automatically break into the debugger.
48+
When an activity arrives, it will automatically break into the debugger.
4949

5050
When breakpoints are used, the debugger may offer extra diagnostic information relevant to the triggering event, available as function arguments.
5151

5252
### Debug context
5353

5454
While in the debugger, the `__DEBUG_CONTEXT__` variable contains various data useful for diagnostic purpose.
5555

56-
| Component | Debug context | Description |
57-
| -------------- | ---------------------------- | -------------------------------- |
58-
| Root container | `{ activities: Activity[] }` | All messages in the chat history |
59-
| Activity | `{ activity: Activity }` | The current message |
56+
| Component | Debug context | Description |
57+
| -------------- | ---------------------------- | ---------------------------------- |
58+
| Root container | `{ activities: Activity[] }` | All activities in the chat history |
59+
| Activity | `{ activity: Activity }` | The current message |
6060

6161
## Recipes
6262

@@ -76,7 +76,7 @@ $$('article').at(-1).webChat.debugger;
7676

7777
Note: `$$()` will select all elements and put them into an array, while `$()` only select the first occurrence.
7878

79-
### Break into debugger when an activity arrive
79+
### Break into debugger when an activity arrives
8080

8181
```js
8282
debug($('.webchat').webChat.breakpoint.incomingActivity);

0 commit comments

Comments
 (0)