From a622fce07338e2eae90764477bb96e420e3a3d8a Mon Sep 17 00:00:00 2001 From: Ben Dubuisson Date: Wed, 26 Nov 2014 11:43:49 +1300 Subject: [PATCH] Update 5-dataobject-relationship-management.md typos --- docs/en/tutorials/5-dataobject-relationship-management.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/en/tutorials/5-dataobject-relationship-management.md b/docs/en/tutorials/5-dataobject-relationship-management.md index feea33d67..312a0dc32 100644 --- a/docs/en/tutorials/5-dataobject-relationship-management.md +++ b/docs/en/tutorials/5-dataobject-relationship-management.md @@ -98,7 +98,7 @@ The restriction is enforced through the `$allowed_children` directive. } You might have noticed that we don't specify the relationship -to a project. That's because its already inherited from the parent implementation, +to a project. That's because it's already inherited from the parent implementation, as part of the normal page hierarchy in the CMS. Now that we have created our `ProjectsHolder` and `Project` page types, we'll add some content. @@ -113,7 +113,7 @@ and collect those within a `ProjectsHolder`. But what about creating `Student` records? Since students are related to a single project, we will -allow editing them right the on the CMS interface in the `Project` page type. +allow editing them right on the CMS interface in the `Project` page type. We do this through a powerful field called `[GridField](/reference/grid-field)`. All customization to fields for a page type are managed through a method called `getCMSFields()`, so let's add it there: