From 8b7de9e69f2418ef9747aa4ca51f59efff9d669c Mon Sep 17 00:00:00 2001 From: Pepe Cano Date: Sat, 10 Nov 2018 01:32:13 +0100 Subject: [PATCH] Rephrase doc --- addon/-private/system/relationships/belongs-to.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/addon/-private/system/relationships/belongs-to.js b/addon/-private/system/relationships/belongs-to.js index e90bee1ec54..21de15f0062 100644 --- a/addon/-private/system/relationships/belongs-to.js +++ b/addon/-private/system/relationships/belongs-to.js @@ -87,7 +87,7 @@ import { DEBUG } from '@glimmer/env'; In contrast to async relationship, accessing a sync relationship will always return the record (Model instance) for the existing local resource, or null. But it will error on access when - a related resource is known to exist but has not been loaded. + a related resource is known to exist and it has not been loaded. ``` let post = comment.get('post');