Fixed typos

Author: Immo Landwerth

accepted/2021/preview-features/preview-features.md

@@ -301,10 +301,10 @@ based on it. This means we can't support them:
 * This also means that people using preview feature in an LTS, they may no
   longer be able to use the latest tooling if the later version of the tooling
   made a breaking change for a preview feature. We consider this acceptable.
-* We don't believe preview features will be around for that long, because the idea is
-  that this only includes features that are on track for productization in the
-  very next release of the platform. This is how it has worked for compiler
-  previews as well.
+* We don't believe preview features will be around for that long, because the
+  idea is that this only includes features that are on track for productization
+  in the very next release of the platform. This is how it has worked for
+  compiler previews as well.
 
 ### What is the quality bar for preview features?
 
@@ -336,7 +336,7 @@ make promises and reserve the right to make changes.
 Halfway through a release cycle we might also decide that certain features won't
 make the cut for RTM quality and we might decide to mark features we shipped in
 a previous preview as `[RequiresPreviewFeatures]`. The reverse is also possible
-(and argubly not a breaking change) but probably less likely.
+(and arguably not a breaking change) but probably less likely.
 
 ### Why a single on/off switch as opposed to individual feature switches?