Replaced H5 request and response sections with H3 in the v1.0 folder#9897
Replaced H5 request and response sections with H3 in the v1.0 folder#9897JarbasHorst wants to merge 2 commits into
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the heading level for request/response subsections within the Example section of a v1.0 API topic to align with the documented standard formatting (H3).
Changes:
- Changed the Example subsection heading from
##### Requestto### Request. - Changed the Example subsection heading from
##### Responseto### Response.
|
Learn Build status updates of commit 7a61bce:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| api-reference/v1.0/api/group-list-grouplifecyclepolicies.md | Details |
api-reference/v1.0/api/group-list-grouplifecyclepolicies.md
- Line 2, Column 8: [Warning: duplicate-titles - See documentation]
Title 'List groupLifecyclePolicies - Microsoft Graph v1.0' is duplicated in: 'v1.0/api/group-list-grouplifecyclepolicies.md(2,8), v1.0/api/grouplifecyclepolicy-list.md(2,8)'. Titles must be unique within a docset. - Line 12, Column 1: [Warning: duplicate-h1s - See documentation]
H1 'List groupLifecyclePolicies' is duplicated with other articles: 'v1.0/api/group-list-grouplifecyclepolicies.md(12,1), v1.0/api/grouplifecyclepolicy-list.md(12,1)'. First level headings must be unique within a docset.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
|
Learn Build status updates of commit ebcc90c:
|
|
Hi @Danipocket, this PR is also reviewed and ready. |
Fixed request and response headings for API topics in the v1.0 folder, excluding intune- files.