Skip to content

Commit f2732d9

Browse files
ryanrishisamselikoff
authored andcommitted
fix typo: libary → library
1 parent 9af823d commit f2732d9

File tree

1 file changed

+1
-1
lines changed
  • tests/dummy/app/pods/docs/components/docs-demo

1 file changed

+1
-1
lines changed

tests/dummy/app/pods/docs/components/docs-demo/template.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ It's also an important part of your addon's testing story. If you write demos fo
77
- They verify your addon's behavior
88
- They ensure all of that behavior is working in your docs site, and up-to-date with your addon's actual APIs
99

10-
This saves you from ever having to remember that second step of "updating the docs" every time you change your libary.
10+
This saves you from ever having to remember that second step of "updating the docs" every time you change your library.
1111

1212
Of course, if your addon's components have some edge cases that would muddle up your documentation site too much, you can fall back to using integration tests. But try to keep most of the behavior in the docs pages — that way your users will know about it.
1313

0 commit comments

Comments
 (0)