Skip to content

Commit e350204

Browse files
Merge pull request #17 from ryami333/patch-1
Fix typo in 1-usage.md Credit to @ryami333
2 parents f5c5dc9 + 0e4e158 commit e350204

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

documentation/3-complex-field/1-usage.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ Field::make('complex', 'crb_slide')->add_fields(array(
99
))
1010
```
1111

12-
The example above shows how to make a slide show. We crated a single complex field named `slide`, to which we attached one group of fields that represents a single slide – `title` and `photo`. The user will be able to add multiple rows of title and photo, thus creating a list of slides for the slide show.
12+
The example above shows how to make a slide show. We created a single complex field named `slide`, to which we attached one group of fields that represents a single slide – `title` and `photo`. The user will be able to add multiple rows of title and photo, thus creating a list of slides for the slide show.
1313

1414
A more advanced usage of the complex field is shown below:
1515

@@ -28,4 +28,4 @@ Field::make('complex', 'crb_media_item')
2828

2929
Here we have to create a list of media items, lets say for an art exhibition. There are two types of items – photos (defined by an `image` and a `caption`) and movies (having a `title`, `length` and the `video` file itself). Since items have different properties, we need to define separate group for each one. Groups also must have a name, by which they will be recognized later – `photograph` and `movie`.
3030

31-
As you can see, depending on their usage, complex fields can either contain a single unnamed group or multiple named groups.
31+
As you can see, depending on their usage, complex fields can either contain a single unnamed group or multiple named groups.

0 commit comments

Comments
 (0)