Increase visibility of limitations

[Ausxor]

The limitations should not be included in the introduction, as it is easy to miss. The introduction typically includes a description of the article, and should not contain key information relating to support of the product.

This edit produces a similar structure to https://docs.microsoft.com/en-us/azure/app-service/overview-vnet-integration#limitations.

[prmerger-automator[bot]]

@Ausxor : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[Jak-MS]

@JennyLawrance - Can you review this PR?

IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team

[ShannonLeavitt]

@JennyLawrance - Can you review this old PR and determine whether it needs to be closed or merged?

IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.

@MicrosoftDocs/public-repo-pr-review-team

[v-dirichards]

@JennyLawrance Pull requests can't be merged when there are merge conflicts. After you resolve the conflicts, you can sign off again.

Conflicting files

• articles/container-apps/firewall-integration.md

For help with resolving merge conflicts, refer to the Contributor Guide, or try the Docs Support channel in Teams.

[ShannonLeavitt]

Closing this PR because the introduction has been substantially updated, so these changes no longer apply. @Ausxor - If you'd like to see additional changes in the article, please open a new PR. Thank you for participating in the community!