This repository was archived by the owner on Dec 4, 2017. It is now read-only.
docs(structural-directives): move ng-container section later in page #3367
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is a follow-up to angular#3345 (comment). No changes were done to the `<ng-container>` section prose. @wardbell: @kapunahelewong and I discussed this, and she agrees with the change -- other edits will come in another PR.
kapunahelewong
approved these changes
Mar 10, 2017
Oups, it seems I missed to back propagate some copyedits. Here they are.
|
Oups, it seems that I omitted to back propagate some copyedits. They've been added in the separate "post review" commit. |
kapunahelewong
approved these changes
Mar 10, 2017
|
This will do for now. I'll be revisiting shortly for v.4 to cope with changes to the microsyntax and the move to |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a follow-up to #3345 (comment).
<ng-container>section prose.<ng-container>in between the two).@wardbell: @kapunahelewong and I discussed the section relocation, and she agrees with the change -- other edits to this guide, if any, will come in follow-up PRs.