From 0e4e158efd707f67456984ebf8c11719feae7385 Mon Sep 17 00:00:00 2001 From: ryami333 Date: Mon, 6 Mar 2017 14:13:14 +1300 Subject: [PATCH] Update 1-usage.md Fix typo. --- documentation/3-complex-field/1-usage.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/documentation/3-complex-field/1-usage.md b/documentation/3-complex-field/1-usage.md index 2c6fdad..a873510 100644 --- a/documentation/3-complex-field/1-usage.md +++ b/documentation/3-complex-field/1-usage.md @@ -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: @@ -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. \ No newline at end of file +As you can see, depending on their usage, complex fields can either contain a single unnamed group or multiple named groups.