Skip to content

Commit 1e4bc1b

Browse files
committed
- Minor cleanup
1 parent a4cc453 commit 1e4bc1b

File tree

3 files changed

+7
-6
lines changed

3 files changed

+7
-6
lines changed

src/content/config.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ by the app
2020
- `lifecycle`: allows an app to register callbacks for events that occur in the lifecycle of an installation. When a
2121
lifecycle event is fired, a POST request will be made to the appropriate URL registered for the event. We'll go into
2222
more detail in **Lifecycle Events**
23-
- `modules`: the list of modules this app provides.
23+
- `modules`: extensions for the user interfaces of Jira.
2424
- `postInstallPage`: this is the first page where the user lands after clicking on the `Get Started` link after
2525
installing the app. You can think of this page as the main index page for the app.
2626
- `webhooks`: list of all the webhooks for the Connect app. For this sample app, we've added some Jira webhooks

src/content/lifecycle-events.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -26,11 +26,11 @@ For more information on lifecycle events, please refer to our [documentation](ht
2626

2727
## Validating installation lifecycle requests
2828
An installation secret will be exchanged every time your app is installed or updated. To secure this key exchange
29-
process, the `install` and `uninstall` lifecycle events include JWT tokens in the Authorization header. This JWT token
30-
will be signed with a private key using the RS256(RSA-SHA256) algorithm.
29+
process, the `install` and `uninstall` lifecycle events include **JWT tokens** in the _Authorization header_. This **JWT token**
30+
will be signed with a private key using the _RS256(RSA-SHA256) algorithm_.
3131

32-
To retrieve the publicKey, make a request to the CDN with the kid parameter supplied in the JWT token header. For
32+
To retrieve the publicKey, make a request to the CDN with the kid parameter supplied in the **JWT token** header. For
3333
example, `https://connect-install-keys.atlassian.com/kid`
3434

35-
The best way to see how JWT tokens work with your lifecycle events is to use the [Connect inspector](http://go.atlassian.com/connect-inspector)
35+
The best way to see how **JWT tokens** work with your lifecycle events is to use the [Connect inspector](http://go.atlassian.com/connect-inspector)
3636
to create a temporary app, install it in your cloud development environment and watch the lifecycle events.

src/routes/atlassian-connect.ts

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,8 @@ export const connectAppDescriptor = {
7575
},
7676

7777
/**
78-
* The list of modules this app provides.
78+
* Extensions for the user interfaces of Jira
79+
* like links, panels, pages, permissions, workflows etc.
7980
*/
8081
modules: {
8182
/**

0 commit comments

Comments
 (0)