Skip to content

Conversation

@awestrem
Copy link
Contributor

Align table numbers with headers, and correct flow number in table.

Align table numbers with headers, and correct flow number in table.
@prmerger-automator
Copy link
Contributor

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

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit d5c15d4:

✅ Validation status: passed

File Status Preview URL Details
articles/load-balancer/load-balancer-outbound-connections.md ✅Succeeded

For more details, please refer to the build report.

@ttorble
Copy link
Contributor

ttorble commented Oct 22, 2025

@mbender-ms

Can you review the proposed changes? (The 1s currently render as 1s in the live article.)

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

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

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Oct 22, 2025
@ttorble ttorble requested a review from Copilot October 22, 2025 15:33
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR corrects table numbering inconsistencies in documentation for Azure Load Balancer outbound connections. The changes align flow numbers and method numbers with their respective table headers.

Key Changes:

  • Fixed method numbering in the outbound connection methods table (rows 2-5)
  • Corrected flow number in the SNAT example table (flow 2)

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants