Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

V3 Documentation errors (Collection) #3212

Closed
nullpointerexceptionkek opened this issue Feb 11, 2025 · 1 comment
Closed

V3 Documentation errors (Collection) #3212

nullpointerexceptionkek opened this issue Feb 11, 2025 · 1 comment
Labels
documentation Improvements or additions to documentation
Milestone

Comments

@nullpointerexceptionkek
Copy link
Contributor

nullpointerexceptionkek commented Feb 11, 2025

Link to the Page

No response

Describe the Issue (screenshots encouraged!)

https://next.skeleton.dev/docs/get-started/fundamentals/#importing-component

Spell Error(fom): "Import the component you wish to use fom your framework package of choice, then insert it into your page template."

https://next.skeleton.dev/docs/get-started/fundamentals/#style-props
Spell Error(classses)

https://next.skeleton.dev/docs/get-started/installation/#mixing-ui-libraries

Spell Error(complimenting)

https://next.skeleton.dev/docs/guides/layouts/#real-world-example

Spell Error (Colum Start/End)

[Svelte](/docs/integrations/iconography/react)
Incorrect link

I will have time to PR this in the next few days

@nullpointerexceptionkek nullpointerexceptionkek added the documentation Improvements or additions to documentation label Feb 11, 2025
@endigo9740 endigo9740 added this to the v3.0 (Next) milestone Feb 11, 2025
@endigo9740
Copy link
Contributor

endigo9740 commented Feb 11, 2025

Great finds @nullpointerexceptionkek. Just FYI I do plan to have a reasonably competent copywriter (read: not me) go through and help improve much of the written documentation closer to release. However, I welcome contributions like this. This is the kind of thing we welcome blind PRs for, with no prior consent required.

The only thing I'd caution is if there are notable changes to the structure or message of the page. But that's typically the kind of thing we can provide feedback on in the PR itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants