improving detailed

[get-itips]

closes https://github.com/MicrosoftDocs/office-docs-powershell/issues/7073

[opbld30]

Docs Build status updates of commit 55cd6b4:

✅ Validation status: passed

File	Status	Preview URL	Details
sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSite.md	✅Succeeded	View (sharepoint-ps)

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[ghost]

Is there a reason we're using parentheses in the explainer text?

[get-itips]

Is there a reason we're using parentheses in the explainer text?

What do you propose? :)

[yogkumgit]

@tseward

[ghost]

@get-itips have we previously used this format for other docs? If so, that's fine. I though we had used bullet points + explainer text below the parameter.

[opbld33]

Docs Build status updates of commit 59813be:

✅ Validation status: passed

File	Status	Preview URL	Details
sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSite.md	✅Succeeded	View (sharepoint-ps)

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel

[yogkumgit]

@tseward

[yogkumgit]

Gentle reminder, @tseward please review the changes.

[yogkumgit]

@Kateyanne Please merge this PR. Thanks.

[opbld32]

Docs Build status updates of commit dfca40c:

✅ Validation status: passed

File	Status	Preview URL	Details
sharepoint/sharepoint-ps/sharepoint-online/Get-SPOSite.md	✅Succeeded	View (sharepoint-ps)

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching in the Docs contributor and Admin Guide
• See the frequently asked questions
• Post your question in the Docs support channel