Merge pull request #1359 from prachi237/Kbase

Improved knowledge Base

Author: viniciusdc

src/maintainer/knowledge_base.rst

@@ -88,7 +88,7 @@ Particularities on Windows
 ==========================
 
 This document presents conda-forge and conda-build information and examples
-when building on Windows.
+while building on Windows.
 
 
 Local testing
@@ -98,9 +98,9 @@ The first thing that you should know is that you can locally test Windows
 builds of your packages even if you don’t own a Windows machine. Microsoft
 makes available free, official Windows virtual machines (VMs) `at this website
 <https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/>`_. If you
-are unfamiliar with VM systems or have trouble installing Microsoft’s, please
-use a general web search to investigate — while these topics are beyond the
-scope of this documentation, there is ample discussion of them on the broader
+are unfamiliar with VM systems or have trouble installing Microsoft’s VMs, please
+use a general web search to explore — while these topics are beyond the
+scope of this documentation, there are ample discussions on them on the broader
 Internet.
 
 In order to compile native code (C, C++, etc.) on Windows, you will need to
@@ -116,17 +116,15 @@ versions are:
 While you can obtain these tools by installing the right version of the full
 `Visual Studio <https://visualstudio.microsoft.com/>`_ development
 environment, you can save a lot of time and bandwidth by installing standalone
-“build tools” packages. The links are:
+“build tools” packages. The links are as follows:
 
 * For Python 2.7: `Microsoft Visual C++ Compiler for Python 2.7
   <https://www.microsoft.com/download/details.aspx?id=44266>`_.
 * For Python 3.5–3.7: `Microsoft Build Tools for Visual Studio 2017
   <https://www.visualstudio.com/downloads/#build-tools-for-visual-studio-2017>`_.
 
-Please see `the Python wiki page on Windows compilers
-<https://wiki.python.org/moin/WindowsCompilers>`_ if you need more
-information.
-
+If you need more information. Please refer `the Python wiki page on Windows compilers
+<https://wiki.python.org/moin/WindowsCompilers>`.
 
 Simple CMake-Based ``bld.bat``
 ------------------------------
@@ -163,7 +161,7 @@ build for such projects.
 The following feedstocks are examples of this build structure deployed:
 
 * `libpng <https://github.com/conda-forge/libpng-feedstock/blob/master/recipe/bld.bat>`_
-* `pugixml <https://github.com/conda-forge/pugixml-feedstock/blob/master/recipe/bld.bat>`_
+* `Pugixml <https://github.com/conda-forge/pugixml-feedstock/blob/master/recipe/bld.bat>`_
 
 
 Building for different VC versions
@@ -206,9 +204,9 @@ Compilers are dependencies with a special syntax and are always added to ``requi
 
 There are currently three supported compilers:
 
- - c
+ - C
  - cxx
- - fortran
+ - Fortran
 
 A package that needs all three compilers would define
 
@@ -223,7 +221,7 @@ A package that needs all three compilers would define
 .. note::
 
   Appropriate compiler runtime packages will be automatically added to the package's runtime requirements and therefore
-  there's no need to specify ``libgcc`` or ``libgfortran``. There is additional information about how conda-build 3 treats
+  there's no need to specify ``libgcc`` or ``libgfortran``. There are additional informations about how conda-build 3 treats
   compilers in the `conda docs <https://docs.conda.io/projects/conda-build/en/latest/source/compiler-tools.html>`_.
 
 .. _cdt_packages:
@@ -232,10 +230,13 @@ Core Dependency Tree Packages (CDTs)
 ------------------------------------
 
 Dependencies outside of the ``conda-forge`` channel should be avoided (see :ref:`no_external_deps`).
-However, there are a few exceptions: some dependencies are so close to the system
-that they are not packaged with ``conda-forge``. These dependencies have to be satisfied with
-*Core Dependency Tree* (CDT) packages. A CDT package consists of repackaged CentOS binaries from the
-appropriate version, either 6 or 7 depending on user choice and platform. We manage the build of CDT
+However, there are a few exceptions: 
+
+Some dependencies are so close to the system that they are not packaged with ``conda-forge``. 
+These dependencies have to be satisfied with *Core Dependency Tree* (CDT) packages. 
+
+A CDT package consists of repackaged CentOS binaries from the appropriate version, 
+either 6 or 7 depending on user choice and platform. We manage the build of CDT
 packages using a centralized repo, `conda-forge/cdt-builds <https://github.com/conda-forge/cdt-builds>`_,
 as opposed to generating feedstocks for them. (Note that historically we did use feedstocks but this
 practice has been deprecated.) To add a new CDT, make a PR on the