final proof read

Author: bishabosha

_overviews/contribute/add-guides.md

@@ -6,7 +6,7 @@ num: 7
 ## Why Contribute New Learning Material?
 
 As [Heather Miller writes][why-contribute], contributing to [docs.scala-lang.org][home] is
-critical to making Scala accessible to newcomers, experience programmers, and anyone who is curious.
+critical to making Scala accessible to newcomers, experienced programmers, and anyone who is curious.
 It is also a fantastic way to contribute for anyone who is comfortable using Scala, but maybe does not want to get
 involved with complex tools like the compiler.
 
@@ -45,7 +45,7 @@ To use this feature you must use the backtick notation as documented by mdoc,
 
 ## Submitting Docs
 
-For you to contribute a document, first
+To contribute a new document, you should first
 [fork](https://help.github.com/articles/fork-a-repo/) the
 [repo](https://github.com/scala/docs.scala-lang), then write your article in
 [Markdown](https://daringfireball.net/projects/markdown/syntax) (example below), and finally submit a pull request.
@@ -87,7 +87,7 @@ is provided.
 The goal of this documentation repository is to be highly curated, rather than the approach by other community-driven
 documentation platforms, like wikis. Therefore, to be included on [docs.scala-lang.org][home], a document must:
 
-- **"fit in"** to the repository ( _i.e.,_ it should not be a complete duplicate of another article),
+- **"fit in"** to the repository (_i.e.,_ it should not be a complete duplicate of another article),
 - **be polished**, i.e. it must be thorough, complete, correct, and organized; written as an article to be understood
   by many users.
 - **be maintained**, if the document might require revisions from time to time, be prepared to keep it up to date, or
@@ -100,8 +100,6 @@ clarifications, etc.
 
 ## Document Templates
 
-> **Note:** These templates will soon change slightly as a result of necessary refactoring.
-
 ### Guides/Overviews
 
 A guide or an overview that can be logically placed on **one** markdown page should be placed in the directory
@@ -215,16 +213,14 @@ snippet and ensures that it's valid.
         <pre class="highlight">
             <code class="hljs scala">&#96;&#96;&#96;scala mdoc
 <span class="hljs-keyword">val</span> a = <span class="hljs-number">1</span>
-&#96;&#96;&#96;
-</code></pre></div></div>
+```</code></pre></div></div>
 
 If you have a snippet that you expect to fail, you can also account for this by
 using `mdoc:fail` for a compile error `mdoc:crash` for a runtime-error.
 
 <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code class="hljs scala">&#96;&#96;&#96;scala mdoc:fail
 <span class="hljs-keyword">val</span> b: <span class="hljs-type">String</span> = <span class="hljs-number">3</span> <span class="hljs-comment">// won't compile</span>
-```
-</code></pre></div></div>
+```</code></pre></div></div>
 
 Keep in mind that a single file is all compiled as a single unit, so you can't
 redefine a variable that was defined above in another code snippet. _However_
@@ -239,28 +235,23 @@ above. Here is an example using the various modifiers.
 
 <span class="hljs-function"><span class="hljs-keyword">def</span> <span class="hljs-title">now</span></span>() = <span class="hljs-type">Instant</span>.now()
 <span class="hljs-class"><span class="hljs-keyword">object</span> <span class="hljs-title">Foo</span> </span>{}
-```
-</code></pre></div></div>
+```</code></pre></div></div>
 
 <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code class="hljs scala">&#96;&#96;&#96;scala mdoc:nest
 <span class="hljs-keyword">case</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">Foo</span>(<span class="hljs-params">a: <span class="hljs-type">Int</span></span>) <span class="hljs-comment">// conflicts with Foo above, but it's nested so it's fine</span></span>
-```
-</code></pre></div></div>
+```</code></pre></div></div>
 
 <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code class="hljs scala">&#96;&#96;&#96;scala mdoc
 <span class="hljs-keyword">val</span> a = <span class="hljs-string">s"The time is <span class="hljs-subst">${now()}</span>"</span> <span class="hljs-comment">// still have access to the now method from above</span>
-```
-</code></pre></div></div>
+```</code></pre></div></div>
 
 <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code class="hljs scala">&#96;&#96;&#96;scala mdoc:reset
 <span class="hljs-keyword">case</span> <span class="hljs-class"><span class="hljs-keyword">class</span> <span class="hljs-title">Foo</span>(<span class="hljs-params">a: <span class="hljs-type">String</span></span>) <span class="hljs-comment">// forget the previous Foo's and start fresh</span></span>
-```
-</code></pre></div></div>
+```</code></pre></div></div>
 
 <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code class="hljs scala">&#96;&#96;&#96;scala mdoc
 <span class="hljs-keyword">val</span> myFoo = <span class="hljs-type">Foo</span>(<span class="hljs-string">"hi"</span>) <span class="hljs-comment">// now we only have access to the last Foo</span>
-```
-</code></pre></div></div>
+```</code></pre></div></div>
 
 [collections-overview]: {% link _overviews/collections-2.13/introduction.md %}
 [why-contribute]: {% link contribute.md %}

_overviews/contribute/bug-reporting-guide.md

@@ -3,15 +3,16 @@ title: Bug Reporting Guide
 num: 8
 ---
 
-The Scala compiler and standard library bug tracker is located at [https://github.com/scala/bug](https://github.com/scala/bug), and for Scala 3, it is located at [github.com/lampepfl/dotty](https://github.com/lampepfl/dotty/issues). Before you submit a bug make sure that it is certainly a bug by following instructions in *Is it a Bug?*.
+The Scala compiler and standard library bug tracker is located at [https://github.com/scala/bug](https://github.com/scala/bug), and for Scala 3, it is located at [github.com/lampepfl/dotty](https://github.com/lampepfl/dotty/issues). Before you submit a bug make sure that it is certainly a bug by following instructions
+in [Is it a Bug?](#is-it-a-bug).
 
 ## Is it a Bug?
 
 The first step in identifying a bug is to identify which component of the Scala distribution is affected. First, ensure that your issue falls within any of the following categories:
 
  - **Library** bugs typically manifest themselves as run-time exceptions, or as *unexpected*/*unintuitive* behavior of Scala Standard Library methods.
  - **Compiler** errors are manifested as compile time exceptions, unexpected behavior of your code at run time, or invalid behavior of the type system.
- - **Reflection** are bugs that appear in the ‘scala.reflect’ package. For the *reflection* bugs , the same rules apply as for the *library* bugs.
+ - **Reflection** are bugs that appear in the `scala.reflect` package. For the *reflection* bugs, the same rules apply as for the *library* bugs.
  - **Scaladoc** bugs are manifested as a logical problems in the information it presents (that is, the displayed information is incorrect, such as an incorrect subclassing relationship), or incorrect behavior of the user interface. If you'd like to suggest a change in the content of the documentation, please submit a pull request (possible to do in the browser using GitHub, which is easier and faster than filing a bug). Please file a bug about the content of documentation only if you cannot provide a suggestion for its fix.
 
 If your issue is related to any of the following external projects, make sure to use its appropriate issue tracker:
@@ -31,13 +32,13 @@ If you have a code snippet that is resulting in bytecode which you believe is be
 
 * Make sure you minimize your problem. To correctly minimize the problem follow the following instructions:
 
-   1. Gradually take apart the offensive code snippet until you believe you have the simplest representation of your problem.
+   1. Gradually remove parts from the original failing code snippet until you believe you have the simplest representation of your problem.
 
-   2. Ensure that you have decoupled your code snippet from any library that could be introducing the offensive behavior. One way to achieve this is to try to recompile the offensive code snippet in isolation, outside of the context of any complex build environment. If your code depends on some strictly Java library and source code is available for it, make sure that the latter is also minimized.
+   2. Ensure that you have decoupled your code snippet from any library that could be introducing the incorrect behavior. One way to achieve this is to try to recompile the offending code snippet in isolation, outside of the context of any complex build environment. If your code depends on some strictly Java library and source code is available for it, make sure that the latter is also minimized.
 
    3. Make sure you are compiling your project from a clean slate. Your problem could be related to separate compilation, which is difficult to detect without a clean build with new `.class` files.
 
-   4. If you have encountered a bug while building your code in the IDE, then please reproduce it on the command line. The same rule applies for build tools like `sbt` or `ant`.
+   4. If you have encountered a bug while building your code in the IDE, then please reproduce it on the command line. The same rule applies for build tools like **sbt** or **Mill**.
 
    5. If you want to file an improvement in the issue tracker please discuss it first on one of the mailing lists. They offer much bigger audience than issue tracker. The latter is not suitable for long discussions.
 
@@ -69,7 +70,7 @@ Please make sure to fill in as many fields as possible. Make sure you've indicat
  3. **Labels** related to your issue. For example, if you think your issue is related to the typechecker, and if you have successfully minimized your issue, label your bug as "typechecker" and "minimized". Issue tracker will suggest names for existing labels as you type them so try not to create duplicates.
  4. **Running environment**. Are you running on Linux? Windows? What JVM version are you using?
 
-In order for us to quickly triage the bug that you've found, it's important that the code snippet which produces the observed issue is as minimized as possible. For advice on minimizing your code snippet, please see the appropriate subsection of the above (Is it a Bug?).
+In order for us to quickly triage the bug that you've found, it's important that the code snippet which produces the observed issue is as minimized as possible. For advice on minimizing your code snippet, please see the appropriate subsection of the above ([Is it a Bug?](#is-it-a-bug)).
 
 ### Description
 

_overviews/contribute/corelibs.md

@@ -14,7 +14,7 @@ There are several options for contributing to Scala's core libraries. You can:
 ### Significant changes
 
 For significant new functionality or a whole new API to be considered for inclusion in the core Scala distribution,
-please take into account [https://github.com/scala/scala-dev/issues/661] before doing so.
+please take into account [scala/scala-dev#661](https://github.com/scala/scala-dev/issues/661) before doing so.
 
 [documentation]: {% link _overviews/contribute/documentation.md %}
 [bug-reporting-guide]: {% link _overviews/contribute/bug-reporting-guide.md %}

_overviews/contribute/documentation.md

@@ -7,10 +7,10 @@ num: 5
 There are several ways you can help out with the improvement of Scala documentation. These include:
 
 * API Documentation in Scaladoc
-* Guides, Overviews, Tutorials, Cheat Sheets and more on the docs.scala-lang.org site
-* Updating scala-lang.org
+* Guides, Overviews, Tutorials, Cheat Sheets and more on the [docs.scala-lang.org][home] site
+* Updating [scala-lang.org](https://scala-lang.org)
 
-Please read this page, and the pages linked from this one, fully before contributing documentation. Many of the questions you have will be answered in these resources. If you have a question that isn't answered, feel free to ask on the [Scala Contributors](https://contributors.scala-lang.org/) mailing list and then, please, submit a pull request with updated documentation reflecting that answer.
+Please read this page, and the pages linked from this one, fully before contributing documentation. Many frequently asked questions will be answered in these resources. If you have a question that isn't answered, feel free to ask on the [Scala Contributors](https://contributors.scala-lang.org/) forum and then, please, submit a pull request with updated documentation reflecting that answer.
 
 **General requirements** for documentation submissions include spell-checking all written language, ensuring code samples compile and run correctly, correct grammar, and clean formatting/layout of the documentation.
 

_overviews/contribute/guide.md

@@ -18,7 +18,7 @@ num: 10
 Just to name a few common reasons:
 
 * contributing a patch is the best way to make sure your desired changes will be available in the next Scala version
-* Scala is written in Scala, so going through the source code and patching it will improve your Scala-fu
+* Scala is written in Scala, so going through the source code and patching it will improve your knowledge of Scala.
 * last but not least, it only takes a few accepted commits to make it into the [Scala Contributor Hall of Fame](https://github.com/scala/scala/contributors).
 
 The main Scala project consists of the standard Scala library, the Scala reflection and macros library,