Skip to content

Commit d68e82c

Browse files
committed
Fix small typos in leptos-0.7 branch
1 parent 3b7eb26 commit d68e82c

1 file changed

Lines changed: 6 additions & 6 deletions

File tree

src/lib.rs

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@
7373
//!
7474
//! # Data Providers
7575
//!
76-
//! As shown in the inital usage example, when you add `#[table(impl_vec_data_provider)]` to your struct,
76+
//! As shown in the initial usage example, when you add `#[table(impl_vec_data_provider)]` to your struct,
7777
//! the table will automatically generate a data provider for you. You can then directly pass a `Vec<T>` to the `rows` prop.
7878
//! Internally this implements the trait [`TableDataProvider`] for `Vec<T>`.
7979
//!
@@ -112,9 +112,9 @@
112112
//!
113113
//! These attributes can be applied to any field in the struct.
114114
//!
115-
//! - **`class`** - Specifies the classes that are applied to each cell (head and body) in the field's column. Can be used in conjuction with `classes_provider` to customize the classes.
116-
//! - **`head_class`** - Specifies the classes that are applied to the header cell in the field's column. Can be used in conjuction with `classes_provider` to customize the classes.
117-
//! - **`cell_class`** - Specifies the classes that are applied to the body cells in the field's column. Can be used in conjuction with `classes_provider` to customize the classes.
115+
//! - **`class`** - Specifies the classes that are applied to each cell (head and body) in the field's column. Can be used in conjunction with `classes_provider` to customize the classes.
116+
//! - **`head_class`** - Specifies the classes that are applied to the header cell in the field's column. Can be used in conjunction with `classes_provider` to customize the classes.
117+
//! - **`cell_class`** - Specifies the classes that are applied to the body cells in the field's column. Can be used in conjunction with `classes_provider` to customize the classes.
118118
//! - **`skip`** - Specifies that the field should be skipped. This is useful for fields that are not displayed in the table.
119119
//! - **`skip_sort`** - Only applies if `sortable` is set on the struct. Specifies that the field should not be used for sorting. Clicking it's header will not do anything.
120120
//! - **`skip_header`** - Makes the title of the field not be displayed in the head row.
@@ -170,7 +170,7 @@ pub struct TemperatureMeasurement {
170170
//! # Classes Customization
171171
//!
172172
//! Classes can be easily customized by using the `classes_provider` attribute on the struct.
173-
//! You can specify any type that implementats the trait [`TableClassesProvider`]. Please see the documentation for that trait for more information.
173+
//! You can specify any type that implements the trait [`TableClassesProvider`]. Please see the documentation for that trait for more information.
174174
//! You can also look at [`TailwindClassesPreset`] for an example how this can be implemented.
175175
//!
176176
//! Example:
@@ -243,7 +243,7 @@ pub struct TemperatureMeasurement {
243243
//! ## When to use `FieldGetter` vs `getter` attribute
244244
//!
245245
//! A field of type `FieldGetter<T>` is a virtual field that doesn't really exist on the struct.
246-
//! Internally `FieldGetter` is just a new-typed `PhatomData` and thus is removed during compilation.
246+
//! Internally `FieldGetter` is just a new-typed `PhantomData` and thus is removed during compilation.
247247
//! Hence it doesn't increase memory usage. That means you should use it for purely derived data.
248248
//!
249249
//! The `getter` attribute should be used on a field that actually exists on the struct but whose

0 commit comments

Comments
 (0)