Merge branch 'main' into iot/docUpdates

FaithOmbongi · web-flow · commit f2a8a43819d1 · 2025-01-17T11:18:27.000+03:00
diff --git a/concepts/changenotifications-for-callrecords.md b/concepts/changenotifications-for-callrecords.md
@@ -38,9 +38,9 @@ Content-Type: application/json
 }
 ```
 
-Change notifications for call records support both `create` and `update` notification types. A subscription for `create` changes only sends a single notification when a call record is first generated. A call record is created after a call or meeting ends and remains accessible for 30 days. 
+Change notifications for call records support both `create` and `update` notification types. A subscription for `create` changes only sends a single notification when a call record is first seen on a particular subscription. A call record is created after a call or meeting ends and remains accessible for 30 days. 
 
-A subscription for `update` changes includes an initial notification when the record is first generated and any subsequent notifications as that record is modified. Because specific call record attributes depend on client-side signals, which can be subject to delays or interruptions due to network issues, a call record might undergo updates with new or revised information after its initial creation. These changes trigger an `update` notification, and the record's `version` field is incremented to indicate the modification.
+A subscription for `update` changes includes an initial notification when the record is first seen on a particular subscription and any subsequent notifications as that record is modified. Because specific call record attributes depend on client-side signals, which can be subject to delays or interruptions due to network issues, a call record might undergo updates with new or revised information after its initial creation. These changes trigger an `update` notification, and the record's `version` field is incremented to indicate the modification.
 
 The latency of change notifications and the maximum subscription expiration period are defined in the [change notifications overview](/graph/webhooks).
 
diff --git a/concepts/toc.yml b/concepts/toc.yml
@@ -567,7 +567,7 @@ items:
       href: connecting-external-content-build-quickstart.yml
       displayName: connectors, Microsoft Graph connectors
     - name: Connectors samples
-      href: /samples/browse/?products=microsoft-graph-connectors-api
+      href: /samples/browse/?terms=graph%20connectors
     - name: Community connectors samples
       href: https://adoption.microsoft.com/sample-solution-gallery/?product=Microsoft+Graph+connectors
     - name: Build your first custom connector using SDK

Original file line number	Diff line number	Diff line change
`@@ -38,9 +38,9 @@ Content-Type: application/json`
`38`	`38`	`}`
`39`	`39`	```
`40`	`40`
`41`		-Change notifications for call records support both `create` and `update` notification types. A subscription for `create` changes only sends a single notification when a call record is first generated. A call record is created after a call or meeting ends and remains accessible for 30 days.
	`41`	+Change notifications for call records support both `create` and `update` notification types. A subscription for `create` changes only sends a single notification when a call record is first seen on a particular subscription. A call record is created after a call or meeting ends and remains accessible for 30 days.
`42`	`42`
`43`		-A subscription for `update` changes includes an initial notification when the record is first generated and any subsequent notifications as that record is modified. Because specific call record attributes depend on client-side signals, which can be subject to delays or interruptions due to network issues, a call record might undergo updates with new or revised information after its initial creation. These changes trigger an `update` notification, and the record's `version` field is incremented to indicate the modification.
	`43`	+A subscription for `update` changes includes an initial notification when the record is first seen on a particular subscription and any subsequent notifications as that record is modified. Because specific call record attributes depend on client-side signals, which can be subject to delays or interruptions due to network issues, a call record might undergo updates with new or revised information after its initial creation. These changes trigger an `update` notification, and the record's `version` field is incremented to indicate the modification.
`44`	`44`
`45`	`45`	`The latency of change notifications and the maximum subscription expiration period are defined in the [change notifications overview](/graph/webhooks).`
`46`	`46`