fix: knowledgebase -> knowledge base
This commit is contained in:
@@ -71,7 +71,7 @@ class Events extends React.Component<Props> {
|
|||||||
<h1>Audit Log</h1>
|
<h1>Audit Log</h1>
|
||||||
<HelpText>
|
<HelpText>
|
||||||
The audit log details the history of security related and other events
|
The audit log details the history of security related and other events
|
||||||
across your knowledgebase.
|
across your knowledge base.
|
||||||
</HelpText>
|
</HelpText>
|
||||||
|
|
||||||
<Tabs>
|
<Tabs>
|
||||||
|
|||||||
@@ -45,7 +45,7 @@ class Export extends React.Component<Props> {
|
|||||||
<h1>Export Data</h1>
|
<h1>Export Data</h1>
|
||||||
<HelpText>
|
<HelpText>
|
||||||
Exporting your team’s documents may take a little time depending on
|
Exporting your team’s documents may take a little time depending on
|
||||||
the size of your knowledgebase. Consider exporting a single document
|
the size of your knowledge base. Consider exporting a single document
|
||||||
or collection instead.
|
or collection instead.
|
||||||
</HelpText>
|
</HelpText>
|
||||||
<HelpText>
|
<HelpText>
|
||||||
|
|||||||
@@ -66,7 +66,7 @@ class Security extends React.Component<Props> {
|
|||||||
<h1>Security</h1>
|
<h1>Security</h1>
|
||||||
<HelpText>
|
<HelpText>
|
||||||
Settings that impact the access, security, and content of your
|
Settings that impact the access, security, and content of your
|
||||||
knowledgebase.
|
knowledge base.
|
||||||
</HelpText>
|
</HelpText>
|
||||||
|
|
||||||
<Checkbox
|
<Checkbox
|
||||||
|
|||||||
@@ -116,7 +116,7 @@ router.post("hooks.slack", async ctx => {
|
|||||||
attachments: [
|
attachments: [
|
||||||
{
|
{
|
||||||
text:
|
text:
|
||||||
"To search your knowledgebase use `/outline keyword`. \nYou’ve already learned how to get help with `/outline help`.",
|
"To search your knowledge base use `/outline keyword`. \nYou’ve already learned how to get help with `/outline help`.",
|
||||||
},
|
},
|
||||||
],
|
],
|
||||||
};
|
};
|
||||||
|
|||||||
@@ -118,7 +118,7 @@ export class Mailer {
|
|||||||
to: opts.to,
|
to: opts.to,
|
||||||
title: `${opts.actorName} invited you to join ${
|
title: `${opts.actorName} invited you to join ${
|
||||||
opts.teamName
|
opts.teamName
|
||||||
}’s knowledgebase`,
|
}’s knowledge base`,
|
||||||
previewText:
|
previewText:
|
||||||
"Outline is a place for your team to build and share knowledge.",
|
"Outline is a place for your team to build and share knowledge.",
|
||||||
html: <InviteEmail {...opts} />,
|
html: <InviteEmail {...opts} />,
|
||||||
|
|||||||
@@ -10,7 +10,7 @@ Outline is a place to build your team knowledge base, you could think of it like
|
|||||||
|
|
||||||
## Structure
|
## Structure
|
||||||
|
|
||||||
Outline allows you to organize documents in "collections", for example these could represent topics like Sales, Product, or HR. Within collections documents can be interlinked and deeply nested to easily build relationships within your knowledgebase.
|
Outline allows you to organize documents in "collections", for example these could represent topics like Sales, Product, or HR. Within collections documents can be interlinked and deeply nested to easily build relationships within your knowledge base.
|
||||||
|
|
||||||
## Search
|
## Search
|
||||||
|
|
||||||
|
|||||||
@@ -8,7 +8,7 @@ Our integration code is also [open-source](https://github.com/outline/outline) a
|
|||||||
|
|
||||||
## Slack
|
## Slack
|
||||||
|
|
||||||
If your team is using Slack to communicate then you’ll definitely want to enable our [Slack Integration](/settings/integrations/slack) to get instant link unfurling for Outline documents and access to the `/outline` slash command to search your knowledgebase directly from Slack.
|
If your team is using Slack to communicate then you’ll definitely want to enable our [Slack Integration](/settings/integrations/slack) to get instant link unfurling for Outline documents and access to the `/outline` slash command to search your knowledge base directly from Slack.
|
||||||
|
|
||||||
## API
|
## API
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user