Skip to content

Commit 6c33e70

Browse files
terrajobstAustinWiseWeihanLi
authored
Apply suggestions for typos
Co-authored-by: Austin Wise <AustinWise@gmail.com> Co-authored-by: Weihan Li <weihanli@outlook.com>
1 parent 02065da commit 6c33e70

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

accepted/2024/net-standard-recommendation.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ However, we have found that many customers still target .NET Standard 1.x. We
2222
found out the reasons boil down to one of two things:
2323

2424
1. Targeting the lowest possible versions is considered better
25-
2. It was like and there is no reason to change
25+
2. It was already like that and there is no reason to change
2626

2727
The first argument has merit in a world where .NET Standard continues to produce
2828
new versions. Since that's no longer the case you might as well update to a
@@ -44,7 +44,7 @@ because code completion simply didn't advertise them.
4444
Jackie is assigned a work item to add a feature that requires writing code in
4545
the shared business logic project. That project happens to target .NET Standard
4646
1.4. She doesn't know why because the project was built before her time on the
47-
team. The fist time she compiles in Visual Studio she sees a warning:
47+
team. The first time she compiles in Visual Studio she sees a warning:
4848

4949
> warning NETSDK1234: Contoso.BusinessLogic.csproj: Targeting .NET Standard
5050
> prior to 2.0 is no longer recommended. See \<URL\> for more details.

0 commit comments

Comments
 (0)