Update tutorial/markdown/couchbase-server/best-practices/json-data-modeling-guide/05-json-design-choices.md

mgroves · gemini-code-assist[bot] · web-flow · commit 78571fb1312f · 2025-08-01T10:13:17.000-04:00
Co-authored-by: gemini-code-assist[bot] &lt;176961590+gemini-code-assist[bot]@users.noreply.github.com&gt;
diff --git a/tutorial/markdown/couchbase-server/best-practices/json-data-modeling-guide/05-json-design-choices.md b/tutorial/markdown/couchbase-server/best-practices/json-data-modeling-guide/05-json-design-choices.md
@@ -166,7 +166,7 @@ Array values may be _simple_ or _object_.
 
 - Another approach is to nest a summary (copy some of the attributes from other documents) to avoid a lookup/join
   - There are lot of advantages in this approach over the first one. In this choice, only _one_ get is required to retrieve all the information that we need regarding the playlist.
-  - However, is this copied data is changed often, it might not be worth duplicating data
+  - However, if this copied data is changed often, it might not be worth duplicating data
 
 ```json
 {

Original file line number	Diff line number	Diff line change
`@@ -166,7 +166,7 @@ Array values may be _simple_ or _object_.`
`166`	`166`
`167`	`167`	`- Another approach is to nest a summary (copy some of the attributes from other documents) to avoid a lookup/join`
`168`	`168`	`- There are lot of advantages in this approach over the first one. In this choice, only _one_ get is required to retrieve all the information that we need regarding the playlist.`
`169`		`- - However, is this copied data is changed often, it might not be worth duplicating data`
	`169`	`+ - However, if this copied data is changed often, it might not be worth duplicating data`
`170`	`170`
`171`	`171`	```json
`172`	`172`	`{`