Fix typos and address review sugesions

Author: WojciechMazur

compiler/src/dotty/tools/dotc/config/Feature.scala

@@ -264,7 +264,7 @@ object Feature:
       if previewSym.exists
       then i"$previewSym is marked @preview$msg"
       else i"$sym inherits @preview$msg"
-    report.error(markedPreview + "\n\n" + previewUseSite("definition"), srcPos)
+    report.error(i"${markedPreview}\n\n${previewUseSite("definition")}", srcPos)
 
   private def previewUseSite(which: String): String =
     s"Preview $which may only be used when compiling with the `-preview` compiler flag"

docs/_docs/reference/other-new-features/preview-defs.md

@@ -6,16 +6,16 @@ nightlyOf: https://docs.scala-lang.org/scala3/reference/other-new-features/previ
 
 New Scala language features or standard library APIs are initially introduced as experimental, but once they become fully implemented and acceppted by the [SIP](https://docs.scala-lang.org/sips/) these can become a preview features.
 Preview language features and APIs are guaranteed to be standarized in some next Scala minor release, but allow compiler team to introduce small, possibly binary incompatible, changes based on the community feedback.
-These can be used by early adopters who can accept possibility of binary compatibility breakage. As an example these can be used for project internal tools and applications, but are discouraged to be used by libraries.
+These can be used by early adopters who can accept the possibility of binary compatibility breakage. For instance, preview features could be used in some internal tool or application. On the other hand, preview features are discouraged in publicly available libraries.
 
-Users can enable access to preview features and definitions by compiling with `-preview` flag. The flag would enable all preview features and definitions. There is no way for enabling only a subset of preview features.
+Users can enable access to preview features and definitions by compiling with the `-preview` flag. The flag would enable all preview features and definitions. There is no scheme for enabling only a subset of preview features.
 
-The biggest difference of preview features when compared with experimental features is their non-viral behaviour.
-Any defintion compiled in the preview mode (using `-preview` flag) is not marked as preview defintion itself.
+The biggest difference of preview features compared to experimental features is their non-viral behaviour.
+A definition compiled in preview mode (using the `-preview` flag) is not marked as a preview definition itself.
 This behaviour allows to use preview features transitively in other compilation units without explicitlly enabled preview mode, as long as it does not directly reference APIs or features marked as preview.
 
-The [`@preview`](https://scala-lang.org/api/3.x/scala/annotation/internal/preview.html) annotations are used to mark Scala 3 standard library APIs currently available under enabled preview mode.
-The definitions follows similar rules as the [`@experimental`](https://scala-lang.org/api/3.x/scala/annotation/experimental.html) when it comes to accessing, subtyping, overriding or overloading definitions marked with this annotation - all of these can only be performed in compilation unit that enables preview mode.
+The [`@preview`](https://scala-lang.org/api/3.x/scala/annotation/internal/preview.html) annotation is used to mark Scala 3 standard library APIs currently available under preview mode.
+The rules for `@preview` are similar to [`@experimental`](https://scala-lang.org/api/3.x/scala/annotation/experimental.html) when it comes to accessing, subtyping, overriding or overloading definitions marked with this annotation - all of these can only be performed in compilation units that enable preview mode.
 
 ```scala
 //> using options -preview