Skip to content

Commit cf60c16

Browse files
committed
update docusaurus
1 parent a921ad5 commit cf60c16

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

website/src/pages/index.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -68,9 +68,9 @@ The Style Guide assumes the use of, but is not limited to:
6868
When creating types, consider how they would best **describe our code**.
6969
Being expressive and keeping types as **narrow as possible** offers several benefits to the codebase:
7070

71-
- Increased Type Safety - Catch errors at compile-time, since narrowed types provide more specific information about the shape and behavior of your data.
72-
- Improved Code Clarity - Cognitive load is reduced by providing clearer boundaries and constraints on your data which makes your code easier to understand by other developers.
73-
- Easier Refactoring - Refactor with confidence, since types are narrow, making changes to your code becomes less risky.
71+
- Increased Type Safety - Catch errors at compile time, as narrowed types provide more specific information about the shape and behavior of your data.
72+
- Improved Code Clarity - Reduces cognitive load by providing clearer boundaries and constraints on your data, making your code easier for other developers to understand.
73+
- Easier Refactoring - With narrower types, making changes to your code becomes less risky, allowing you to refactor with confidence.
7474
- Optimized Performance - In some cases, narrow types can help the TypeScript compiler generate more optimized JavaScript code.
7575

7676
### Type Inference

0 commit comments

Comments
 (0)