Skip to content

Commit c379165

Browse files
committed
minor grammar fixes
1 parent 2c53808 commit c379165

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

fern/docs/pages/tutorials/perform-external-action.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
## Introduction
22

3-
In this tutorial, you'll lean how to develop a snap-in that mirrors an issue from
3+
In this tutorial, you'll learn how to develop a snap-in that mirrors an issue from
44
DevRev to GitHub. This requires addition of a command that can be run from
55
the **Discussions** tab of an issue in DevRev, which creates an issue in GitHub.
66

@@ -101,7 +101,7 @@ functions:
101101
```
102102
103103
The command clearly states where you can use it. For example, in the
104-
**Discussions** tab of issues.
104+
**Discussions** tab of issues.
105105
106106
It also explains the different situations and
107107
ways in which you can make use of this command.
@@ -126,7 +126,7 @@ name (`RepoName`) before proceeding with the issue creation.
126126

127127
### Function logic
128128

129-
After creating the manifest and establishing the snap-in's logic, the next step is to define the function logic that handles business logic. Once you understand the payload structure of a command, you can proceed with its implementation.
129+
After creating the manifest and establishing the snap-in's logic, the next step is to define the function logic that handles the business logic. Once you understand the payload structure of a command, you can proceed with its implementation.
130130

131131
To proceed, define the handler function for command events.
132132

@@ -291,11 +291,11 @@ Once the code has been validated, the next steps involve creating the snap-in
291291
version and subsequently creating the snap-in itself. Before installing the
292292
snap-in, it's essential to set up a GitHub Personal Access Token (PAT) and add
293293
it to the connections in DevRev as a snap-in secret. Ensure that the secret is
294-
shared within the organization so that the snap-in can utilize it.
294+
shared within the organization so that the snap-in can utilize it.
295295

296296
Follow these steps to install the snap-in in your organization:
297297

298-
#### Step 1: Create a GitHub personal access token
298+
#### Step 1: Create a GitHub personal access token
299299

300300
Generate a GitHub Personal Access Token (PAT) by following the steps outlined in the
301301
[GitHub documentation](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens).

0 commit comments

Comments
 (0)