Addressed a couple of comments

Author: Dan Kershaw [MSFT]

graph/GuidelinesGraph.md

@@ -257,7 +257,7 @@ If possible, APIs SHOULD use resource-based designs with standard HTTP methods r
 |  Microsoft Graph rules for modeling behavior                     |
 |------------------------------------------------------------------|
 | :heavy_check_mark: **MUST** use POST to create new entities in insertable entity sets or collections.<BR>This approach requires the server to produce a system generated key. |
-| :heavy_check_mark: **MAY** use PATCH to create new entities in insertable entity sets or collections.<BR>This [Upsert](./patterns/upsert.md) approach requires the caller to provide a key. |
+| :ballot_box_with_check: **SHOULD** additionally use PATCH to create new entities in insertable entity sets or collections.<BR>This [Upsert](./patterns/upsert.md) approach requires the caller to provide a key. |
 | :heavy_check_mark: **MUST** use PATCH to edit updatable resources.  |
 | :heavy_check_mark: **MUST** use DELETE to delete deletable resources. |
 | :heavy_check_mark: **MUST** use GET for listing and reading resources. |

graph/patterns/default-properties-and-select.md

@@ -0,0 +1,30 @@
+# Default properties and $select
+
+Microsoft Graph API Design Pattern
+
+*Provide a short description of the pattern.*
+
+
+## Problem
+
+*Describe the business context relevant for the pattern.*
+
+*Provide a short description of the problem.*
+
+## Solution
+
+*Describe how to implement the solution to solve the problem.*
+
+*Describe related patterns.*
+
+## When to use this pattern
+
+*Describe when and why the solution is applicable and when it might not be.*
+
+## Issues and considerations
+
+*Describe tradeoffs of the solution.*
+
+## Example
+
+*Provide a short example from real life.*

graph/patterns/upsert.md

@@ -154,6 +154,37 @@ Preference-Applied: idempotent; return=representation
 
 Notice how this operation is idempotent in nature, rather than returning a 409 conflict error.
 
+### Updating a record
+
+Update "Group157" group with a new description.
+
+```http
+PATCH /groups(uniqueName='Group157')
+Prefer: idempotent; return=representation
+```
+
+```json
+{
+    "description": "Some of my favorite people in the world."
+}
+```
+
+Response:
+
+```http
+200 ok
+Preference-Applied: idempotent; return=representation
+```
+
+```json
+{
+    "id": "1a89ade6-9f59-4fea-a139-23f84e3aef66",
+    "displayName": "My favorite group",
+    "description": "Some of my favorite people in the world.",
+    "uniqueName": "Group157"
+}
+```
+
 ### Upsert not supported
 
 Create a new group, with a `uniqueName` of "Group157". In this case, this group does not exist and additionally