Link webhooks and access token pages to documentation
This commit is contained in:
@@ -177,7 +177,7 @@ export default function AccessTokens() {
|
||||
They should be kept secure and never included in client code, instead they should be kept on a server that you control.
|
||||
</Paragraph>
|
||||
<Paragraph>
|
||||
Read more about how to use these tokens at _some documentation here_.
|
||||
Read more about how to use these tokens, with examples, at <a href="https://owncast.online/docs/integrations/">our documentation</a>.
|
||||
</Paragraph>
|
||||
|
||||
<Table rowKey="token" columns={columns} dataSource={tokens} pagination={false} />
|
||||
|
||||
@@ -175,7 +175,7 @@ export default function Webhooks() {
|
||||
A webhook is a callback made to an external API in response to an event. These are endpoints that live outside of Owncast and run code who wants to be made aware of events that take place on your server.
|
||||
</Paragraph>
|
||||
<Paragraph>
|
||||
Read more about how to use webhooks at _some documentation here_.
|
||||
Read more about how to use webhooks, with examples, at <a href="https://owncast.online/docs/integrations/">our documentation</a>.
|
||||
</Paragraph>
|
||||
|
||||
<Table rowKey="id" columns={columns} dataSource={webhooks} pagination={false} />
|
||||
|
||||
Reference in New Issue
Block a user