From f5e5e55f7fde271a2f679a9cace48cb4279e45d2 Mon Sep 17 00:00:00 2001 From: Michael Staib Date: Thu, 1 Aug 2024 17:13:38 +0200 Subject: [PATCH] Update spec/Section 2 -- Source Schema.md Co-authored-by: Glen --- spec/Section 2 -- Source Schema.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec/Section 2 -- Source Schema.md b/spec/Section 2 -- Source Schema.md index a116d5d..7cb48a2 100644 --- a/spec/Section 2 -- Source Schema.md +++ b/spec/Section 2 -- Source Schema.md @@ -141,7 +141,7 @@ type Product @key(fields: "id") { Lookups can also be nested within other lookups and allow resolving nested entities that are part of an aggregate. In the following example the `Product` can be resolved by its ID but also the `ProductPrice` can be resolved by -passing in a composite key containing the product id and region name of the +passing in a composite key containing the product ID and region name of the product price. ```graphql example