Convert FAQ to new YAML format

[sdwheeler]

PR Summary

Fixes AB#1807266 - Convert FAQ to new YAML format

Select the area of the Table of Contents containing the documents being changed.

Conceptual content

• Overview and Install
• Learning PowerShell
  • PowerShell 101
  • Deep dives
  • Remoting
• Release notes (What's New)
• Windows PowerShell
  • WMF, ISE, release notes, etc.
• DSC articles
• Community resources
• Sample scripts
• Gallery articles
• Scripting and development
  • Legacy SDK

Cmdlet reference & about_ topics

• Preview content
• Version 7.1 content
• Version 7.0 content
• Version 5.1 content

PR Checklist

• I have read the contributors guide and followed the style and process guidelines
• PR has a meaningful title
• PR is targeted at the staging branch
• All relevant versions updated
• Includes content related to issues and PRs - see Closing issues using keywords.
• This PR is ready to merge and is not Work in Progress
  • If the PR is work in progress, please add the prefix WIP: or [WIP] to the beginning of the
    title and remove the prefix when the PR is ready.

[opbld33]

Docs Build status updates of commit b4f608c:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
reference/docs-conceptual/gallery/faqs.yml	⚠️Warning	View (>=powershell-5.1)	Details
reference/docs-conceptual/toc.yml	⚠️Warning	View (>=powershell-5.1)	Details
reference/docs-conceptual/gallery/faqs.md	✅Succeeded

reference/docs-conceptual/gallery/faqs.yml

• Line 44, Column 1: [Warning-xref-not-found] Cross reference not found: 'PowershellGet.Publish-Module'.
• Line 45, Column 1: [Warning-xref-not-found] Cross reference not found: 'PowershellGet.Publish-Script'.
• Line 47, Column 1: [Warning-xref-not-found] Cross reference not found: 'PowershellGet.Publish-Module'.
• Line 48, Column 1: [Warning-xref-not-found] Cross reference not found: 'PowershellGet.Publish-Script'.
• Line 97, Column 18: [Warning-xref-not-found] Cross reference not found: 'PowershellGet.Publish-Module'.
• Line 107, Column 3: [Warning-xref-not-found] Cross reference not found: 'PowershellGet.Publish-Module'.
• Line 130, Column 1: [Warning-xref-not-found] Cross reference not found: 'PowershellGet.Publish-Script'.
• Line 139, Column 3: [Warning-xref-not-found] Cross reference not found: 'PowershellGet.Publish-Script'.
• Line 163, Column 1: [Warning-xref-not-found] Cross reference not found: 'PowershellGet.New-ScriptFileInfo'.
• Line 169, Column 1: [Warning-xref-not-found] Cross reference not found: 'PowershellGet.Test-ScriptFileInfo'.
• Line 172, Column 1: [Warning-xref-not-found] Cross reference not found: 'PowershellGet.Update-ScriptFileInfo'.
• Line 204, Column 26: [Warning-xref-not-found] Cross reference not found: 'PowershellGet.Install-Module'.
• Line 207, Column 1: [Warning-xref-not-found] Cross reference not found: 'PowershellGet.Update-Module'.
• Line 208, Column 1: [Warning-xref-not-found] Cross reference not found: 'PowershellGet.Publish-Module'.
• Line 228, Column 1: [Warning-xref-not-found] Cross reference not found: 'PowershellGet.Register-PSRepository'.
• Line 237, Column 33: [Warning-xref-not-found] Cross reference not found: 'PowershellGet.Install-Module'.

reference/docs-conceptual/toc.yml

• Line 771, Column 11: [Warning-file-not-found] Invalid file link: 'gallery/faqs.md'.

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

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.

Note: Your PR may contain errors or warnings 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.

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

[opbld30]

Docs Build status updates of commit 6d15a5c:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
reference/docs-conceptual/toc.yml	⚠️Warning	View (>=powershell-5.1)	Details
reference/docs-conceptual/gallery/faqs.md	✅Succeeded
reference/docs-conceptual/gallery/faqs.yml	✅Succeeded	View (>=powershell-5.1)

reference/docs-conceptual/toc.yml

• Line 771, Column 11: [Warning-file-not-found] Invalid file link: 'gallery/faqs.md'.

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

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.

Note: Your PR may contain errors or warnings 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.

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

[opbld33]

Docs Build status updates of commit b4d8e7d:

✅ Validation status: passed

File	Status	Preview URL	Details
reference/docs-conceptual/gallery/faqs.md	✅Succeeded
reference/docs-conceptual/gallery/faqs.yml	✅Succeeded	View (>=powershell-5.1)
reference/docs-conceptual/toc.yml	✅Succeeded	View (>=powershell-5.1)

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