Skip to content

Commit 1f593ab

Browse files
authored
docs: fix typos in addons/ (#72)
1 parent 1821696 commit 1f593ab

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

Diff for: addons/use.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Use Addon
22

3-
Addons are sets of additionnal components, layouts, styles, configuration...etc. that you can use in your presentation.
3+
Addons are sets of additional components, layouts, styles, configuration...etc. that you can use in your presentation.
44

55
They are quite similar to [themes](/themes/use), but in general:
66

Diff for: addons/write-an-addon.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ An addon can contribute to the following points:
1414

1515
## Conventions
1616

17-
Adons are published to npm registry, and they should follow the conventions below:
17+
Addons are published to npm registry, and they should follow the conventions below:
1818

1919
- Package name should start with `slidev-addon-`, for example: `slidev-addon-awesome`
2020
- Add `slidev-addon` and `slidev` in the `keywords` field of your `package.json`
@@ -49,7 +49,7 @@ And optionally, you can also add some scripts to your `packages.json`
4949
}
5050
```
5151

52-
To publish your theme, simply run `npm publish` and you are good to go. There is no build process required (which means you can directly publish `.vue` and `.ts` files, Slidev is smart enough to understand them).
52+
To publish your addon, simply run `npm publish` and you are good to go. There is no build process required (which means you can directly publish `.vue` and `.ts` files, Slidev is smart enough to understand them).
5353

5454
Addon contribution points follow the same conventions as local customization, please refer to [the docs for the naming conventions](/custom/).
5555

0 commit comments

Comments
 (0)