Skip to content

Commit bbbc358

Browse files
authored
Merge pull request #192 from jakedee/main
fix: Spelling/grammar in default standards
2 parents 2ee3d3c + 01bbcec commit bbbc358

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

profiles/default/standards/frontend/responsive.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
## Responsive design best practices
22

33
- **Mobile-First Development**: Start with mobile layout and progressively enhance for larger screens
4-
- **Standard Breakpoints**: Consistently use standard breakpoints across the application (e.g., mobile, tablet, deskto)
4+
- **Standard Breakpoints**: Consistently use standard breakpoints across the application (e.g., mobile, tablet, desktop)
55
- **Fluid Layouts**: Use percentage-based widths and flexible containers that adapt to screen size
66
- **Relative Units**: Prefer rem/em units over fixed pixels for better scalability and accessibility
7-
- **Test Across Devices**: Test and verify UI changes across multiple screen sizes from mobile to tablet to desktop screen sizes and ensure a balanced, user-friendly viewing and reading experience on all.
7+
- **Test Across Devices**: Test and verify UI changes across multiple screen sizes from mobile to tablet to desktop screen sizes and ensure a balanced, user-friendly viewing and reading experience on all
88
- **Touch-Friendly Design**: Ensure tap targets are appropriately sized (minimum 44x44px) for mobile users
99
- **Performance on Mobile**: Optimize images and assets for mobile network conditions and smaller screens
1010
- **Readable Typography**: Maintain readable font sizes across all breakpoints without requiring zoom

profiles/default/standards/global/commenting.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,4 +2,4 @@
22

33
- **Self-Documenting Code**: Write code that explains itself through clear structure and naming
44
- **Minimal, helpful comments**: Add concise, minimal comments to explain large sections of code logic.
5-
- **Don't comment changes or fixes**: Do not leave code comments that speak to recent or temporary changes or fixes. Comments should be evergreen informtional texts that are relevant far into the future.
5+
- **Don't comment changes or fixes**: Do not leave code comments that speak to recent or temporary changes or fixes. Comments should be evergreen informational texts that are relevant far into the future.

0 commit comments

Comments
 (0)