Skip to content

Commit

Permalink
Update 1-usage.md
Browse files Browse the repository at this point in the history
Fix typo.
  • Loading branch information
ryami333 authored Mar 6, 2017
1 parent f5c5dc9 commit 0e4e158
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions documentation/3-complex-field/1-usage.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ Field::make('complex', 'crb_slide')->add_fields(array(
))
```

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.
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.

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

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

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`.

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

0 comments on commit 0e4e158

Please sign in to comment.