File tree Expand file tree Collapse file tree 2 files changed +2
-2
lines changed
src/System.Management.Automation/engine/hostifaces Expand file tree Collapse file tree 2 files changed +2
-2
lines changed Original file line number Diff line number Diff line change @@ -1816,7 +1816,7 @@ private void ClearHistoryByID()
1816
1816
) ;
1817
1817
}
1818
1818
else
1819
- { // if id,count adn newest parameters are present
1819
+ { // if id,count and newest parameters are present
1820
1820
// throw an exception for invalid count values
1821
1821
1822
1822
long id = _id [ 0 ] ;
Original file line number Diff line number Diff line change @@ -159,7 +159,7 @@ function Get-ChangeLog
159
159
# # and eventually merge the release branch back to the master branch. This will result in different commit nodes
160
160
# # in master branch that actually represent same set of changes.
161
161
# #
162
- # # In this case, we cannot simply use the revision range "$tag_hash..HEAD" becuase it will include the original
162
+ # # In this case, we cannot simply use the revision range "$tag_hash..HEAD" because it will include the original
163
163
# # commits in the master branch that were cherry-picked to the release branch -- they are reachable from 'HEAD'
164
164
# # but not reachable from the last release tag. Instead, we need to exclude the commits that were cherry-picked,
165
165
# # and only include the commits that are not in the last release into the change log.
You can’t perform that action at this time.
0 commit comments