Merge pull request #3736 from joshborut/master

Fixed bullet point capitalization
rrousselGit · Sep 10, 2024 · d4ec5a7 · d4ec5a7
2 parents 98746c7 + 730c3c6
commit d4ec5a7
Show file tree

Hide file tree

Showing 4 changed files with 18 additions and 18 deletions.
diff --git a/website/docs/concepts/about_code_generation.mdx b/website/docs/concepts/about_code_generation.mdx
@@ -113,7 +113,7 @@ You may be wondering: "If code generation is optional in Riverpod, why use it?"
 As always with packages: To make your life easier.
 This includes but is not limited to:
 
-- better syntax, more readable/flexible, and with a reduced learning curve.
+- Better syntax, more readable/flexible, and with a reduced learning curve.
   - No need to worry about the type of provider. Write your logic,
     and Riverpod will pick the most suitable provider for you.
   - The syntax no longer looks like we're defining a "dirty global variable".
@@ -122,9 +122,9 @@ This includes but is not limited to:
     using <Link documentID="concepts/modifiers/family"/> and passing a single positional parameter,
     you can now pass any parameter. This includes named parameters, optional ones,
     and even default values.
-- **stateful hot-reload** of the code written in Riverpod.
-- better debugging, through the generation of extra metadata that the debugger then picks up.
-- some Riverpod features will be available only with code generation.
+- **Stateful hot-reload** of the code written in Riverpod.
+- Better debugging, through the generation of extra metadata that the debugger then picks up.
+- Some Riverpod features will be available only with code generation.
 
 ## The Syntax
 

diff --git a/website/docs/concepts/about_hooks.mdx b/website/docs/concepts/about_hooks.mdx
@@ -53,9 +53,9 @@ by an alterative that does not invole "nesting" – drastically improving readab
 
 In general, hooks are helpful for:
 
-- forms
-- animations
-- reacting to user events
+- Forms
+- Animations
+- Reacting to user events
 - ...
 
 As an example, we could use hooks to manually implement a fade-in animation,

diff --git a/website/docs/essentials/first_request.mdx b/website/docs/essentials/first_request.mdx
@@ -54,10 +54,10 @@ In Riverpod, business logic is placed inside "providers".
 A provider is a super-powered function.
 They behave like normal functions, with the added benefits of:
 
-- being cached
-- offering default error/loading handling
-- being listenable
-- automatically re-executing when some data changes
+- Being cached
+- Offering default error/loading handling
+- Being listenable
+- Automatically re-executing when some data changes
 
 This make providers a perfect fit for _GET_ network requests (as for _POST/etc_ requests, see <Link documentID="essentials/side_effects" />).
 

diff --git a/website/docs/introduction/why_riverpod.mdx b/website/docs/introduction/why_riverpod.mdx
@@ -34,13 +34,13 @@ fairly limited. A number of challenges remain unsolved:
 Nailing those problems at scale can be difficult, and they are impacted by a large
 amount of features, such as:
 
-- pull to refresh
-- infinite lists / fetch as we scroll
-- search as we type
-- debouncing asynchronous requests
-- cancelling asynchronous requests when no-longer used
-- optimistic UIs
-- offline mode
+- Pull to refresh
+- Infinite lists / fetch as we scroll
+- Search as we type
+- Debouncing asynchronous requests
+- Cancelling asynchronous requests when no-longer used
+- Optimistic UIs
+- Offline mode
 - ...
 
 These features can be tricky to implement, but are crucial for a good user experience.