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.

Sign up for GitHub

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

Jump to bottom

docs: fixed some typos #4273

Merged
merged 1 commit into from
Oct 31, 2024
Merged

docs: fixed some typos #4273

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/content/components/form/button/button-press.demo.tsx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ export default () => {
Press me
</Button>
<Text>
Number of times presse: {count} (
Number of times pressed: {count} (
{pointerType
? `Button is pressed via ${pointerType}.`
: 'Button not pressed.'}
Expand Down
4 changes: 2 additions & 2 deletions docs/content/releases/blog/release-2024-10-25.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,7 +125,7 @@ Renamed the `isDateUnavailable` prop to `dateUnavailable` to align with our code
- **Dialog**: The size can now be defined via the `size` prop, instead of being defined by the content of the dialog.
- **Checkbox Group:** The `<Checkbox.Group>` can now be used as a compound component, aligning it with the structure of other components.
- **DatePicker:** Based on the feedback from DSTSUP-94, added styles for unavailable dates to both b2b and core theme. Thanks Daniel!
- **SectionMessage**: Based on the feedback, added posibility to dimiss a `<SectionMessage>`. This is now aligned with our feedback message pattern. Thanks Laura for the suggestion!
- **SectionMessage**: Based on the feedback, added possibility to dimiss a `<SectionMessage>`. This is now aligned with our feedback message pattern. Thanks Laura for the suggestion!
- **XLoader**: The loader now supports to be displayed as a full-screen overlay or as inline loading indicator. Thanks Robert and Indre for the suggestions!

### Types
Expand All @@ -151,7 +151,7 @@ We've introduced several updates to enhance the usability and structure of our d
- **Release Blog:** We now have a release blog, you are currently reading, to keep users informed about recent changes, new features, and important announcements, ensuring they are always up-to-date with the latest information.
- **New Landing Page:** As you may already saw, we provided a new landing page for our documentation. With this user-friendly landing page, we can effectively helps visitors orient themselves, understand the purpose of the design system, and the user can easily navigate to relevant sections.
- **Streamlined Structure:** We also cleaned up the documentation structure, we reduced old content, structured the navigation and tidy up related pages according the new structure.
- **Component Pages:** Of course we also provided more updated guidelines for component pages, like `<SectionMessag>` or `<MarigoldProvider>`.
- **Component Pages:** Of course we also provided more updated guidelines for component pages, like `<SectionMessage>` or `<MarigoldProvider>`.
- **Guidelines:** Added a new page about form fields with some general usage guidelines.
- **Patterns:** Added a new pattern for how to use loading states.

Expand Down
Loading