Skip to content

Commit 39e32f3

Browse files
committed
resolving doc errors
1 parent 11fb07e commit 39e32f3

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

api-reference/beta/resources/restoresessionartifactcount.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,8 +22,8 @@ Represents artifact count metadata of a particular [Restore Session](../resource
2222
|Method|Return type|Description|
2323
|:---|:---|:---|
2424
|[Create](../api/backuprestoreroot-post-sharepointrestoresessions.md)|[sharePointRestoreSession](../resources/sharepointrestoresession.md)|Create a new [sharePointRestoreSession](../resources/sharepointrestoresession.md).|
25-
|[Create](../api/backuprestoreroot-post-onedriveforbusinessrestoresessions.md)|[oneDriveForBusinessRestoreSession](../resources/onedriveforbusinessrestoresessions.md)|Create a new [oneDriveForBusinessRestoreSession](../resources/onedriveforbusinessrestoresessions.md).|
26-
|[Create](../api/backuprestoreroot-post-exchangerestoresessions.md)|[exchangeRestoreSession](../resources/exchangerestoresessions.md)|Create a new [exchangeRestoreSession](../resources/exchangerestoresessions.md).|
25+
|[Create](../api/backuprestoreroot-post-onedriveforbusinessrestoresessions.md)|[oneDriveForBusinessRestoreSession](../resources/onedriveforbusinessrestoresessions.md)|Create a new [oneDriveForBusinessRestoreSession](../resources/onedriveforbusinessrestoresession.md).|
26+
|[Create](../api/backuprestoreroot-post-exchangerestoresessions.md)|[exchangeRestoreSession](../resources/exchangerestoresession.md)|Create a new [exchangeRestoreSession](../resources/exchangerestoresession.md).|
2727
|[List](../api/backuprestoreroot-list-restoresessions.md)|[restoreSessionBase](../resources/restoresessionbase.md) collection|Get a list of [restoreSessionBase](../resources/restoresessionbase.md) objects and their properties.|
2828
|[Get](../api/restoresessionbase-get.md)|[restoreSessionBase](../resources/restoresessionbase.md)|Read the properties and relationships of a [restoreSessionBase](../resources/restoresessionbase.md) object.|
2929
|[Activate](../api/restoresessionbase-activate.md)|[restoreSessionBase](../resources/restoresessionbase.md)|Activate a draft restore session.|
@@ -43,7 +43,7 @@ The following JSON representation shows the resource type.
4343
<!-- {
4444
"blockType": "resource",
4545
"@odata.type": "microsoft.graph.restoreSessionArtifactCount",
46-
"baseType": "microsoft.graph.complextType",
46+
"baseType": "microsoft.graph.complexType",
4747
"openType": false
4848
}
4949
-->

api-reference/beta/resources/sharepointrestoresession.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ Inherits from [restoreSessionBase](../resources/restoresessionbase.md).
4040
|lastModifiedDateTime|DateTimeOffset|Timestamp of last modification of this restore session.|
4141
|status|[restoreSessionStatus](../resources/sharepointrestoresession.md#restoresessionstatus-values)|Status of the restore session. The value is an aggregated status of restore artifacts. The possible values are: `draft`, `activating`, `active`, `completedWithError`, `completed`, `unknownFutureValue`, `failed`. You must use the `Prefer: include-unknown-enum-members` request header to get the following value in this [evolvable enum](/graph/best-practices-concept#handling-future-members-in-evolvable-enumerations): `failed`.|
4242
|restoreJobType|[restoreJobType](../resources/enums.md#restorejobtype-values)|Indicates whether the restore sesssion was created normally or by a bulk job.|
43-
|restoreSessionArtifactCount|[restoreSessionArtifactCount](../resources/restoresessionartifactcount)|The number of metadata artifacts that belong to this restore session.|
43+
|restoreSessionArtifactCount|[restoreSessionArtifactCount](../resources/restoresessionartifactcount.md)|The number of metadata artifacts that belong to this restore session.|
4444

4545
### restoreSessionStatus values
4646

0 commit comments

Comments
 (0)