FAQ improvements

FAQ.mediawiki

@@ -4,21 +4,23 @@ Frequently Asked Questions
 
 ==Can I use Winbuilder to build PhoenixPE?==
 
-No. Winbuilder is no longer developed an contains numerous bugs that have not been fixed, some of which are critical. Winbuilder bugs aside PhoenixPE also makes use of PEBakery exclusive features and additional commands that are not present in Winbuilder.
+No. Winbuilder is no longer developed an contains numerous bugs, some of which are critical. Winbuilder bugs aside PhoenixPE also makes use of PEBakery exclusive features and additional commands that are not present in Winbuilder.
 
 ==Is PhoenixPE a clone/fork of Win10PE_SE/Win10XPE/etc.?==
 
-No. PhoenixPE development started around 2014 as a Winbuilder project and was originally envisioned as a replacement for the Win10PE_SE project, which had become bloated and hard to maintain. In 2016 PhoenixPE was re-written from the ground up for use with the [https://github.com/pebakery/PEBakery PEBakery engine], providing me with the opportunity and challenge of coding a project from scratch without Winbuilder bug workarounds, hacks, and bloat built up over a decade of Vista/7/8/8.1/10 WinPE evolution. It also assisted greatly in the testing, documentation, and development of the PEBakery engine. 
+No. The projects have completely separate origins. 
 
-Win10XPE was released several years later, in March of 2018.
+PhoenixPE development started in 2014 as a Winbuilder project and was originally envisioned as a replacement for the Win10PE_SE project, which had become bloated and hard to maintain. In 2016 PhoenixPE was re-written from the ground up using the new open-source [https://github.com/pebakery/PEBakery PEBakery engine], providing me with the opportunity and challenge of coding a project from scratch without Winbuilder bug workarounds, hacks, and bloat built up over a decade of Vista/7/8/8.1/10 WinPE evolution. The development of PhoenixPE also assisted greatly in the testing, documentation, and development of the PEBakery engine. 
+
+Win10XPE was released as a Winbuilder project several years later in March of 2018, shortly after Misty released ChrisPE as a PEBakery proof-of-concept project. ChrisPE was named as both a play on PEBakery (crispy...PEBakery...get it? ha. ha.) and as a tribute to longtime developer ChrisR after he announced his retirement from maintaining the Win10PE_SE project.
 
 ==Is PhoenixPE a replacement for Win10XPE?==
 
-It's an alternative. Both produce a very similar environment based on decades of community members working together. We aren't in competition.
+It's an alternative. Both produce a similar WinPE environment based on decades of community members working together. We aren't in competition.
 
-In my option the 2 projects have different goals. Win10XPE states that "it's main objective is to be simple, user-friendly and to be as fast as possible". This caters well to user that just want to press a button and get a working PE without much fuss. Win10XPE does great at providing a simple, pre-packaged experience, however it's core codebase is cumbersome and inconsistent and in an effort to provide a simple user experience, it loses the flexibility and ease of customization advanced users crave. 
+Win10XPE does great at providing a simple, pre-packaged experience, however at it's core the code-base is cumbersome and inconsistent and in an effort to provide a simple user experience it loses the flexibility and ease of customization advanced users crave. 
 
-PhoenixPE on the other hand targets basic/advanced users as well as developers looking for more control over how and what goes into their PE. It strives to be simple for both users to build, and for developers to contribute/maintain. 
+PhoenixPE on the other hand targets users and developers looking for more control over how and what goes into their PE. PhoenixPE's modular architecture and robust API combined with the stability and speed of the PEBakery engine make it simple for users of all skill levels to build, flexible enough for the most advanced users to modify/tweak, and easy for developers to maintain. 
 
 '''TL;DR: No. It's an alternative. The developers of both projects are part of a vibrate community that works together and shares their knowledge and experience. Use the one that best meets your needs. You can't go wrong.'''
 
@@ -38,27 +40,27 @@ Unfortunately it's impossible for us to include every conceivable application in
 
 PhoenixPE carefully selects applications we include in the main distribution, taking into account among other criteria: popularity, license, ease of integration, ease of maintenance, and perceived usefulness to the community at large.
 
-The great news is, that with PEBakery's user friendly and flexible scripting language it's relatively easy to make your own scripts and include your favorite applications. Be sure to check out the [https://github.com/pebakery/pebakery-docs PEBakery Documentation] and the [https://github.com/PhoenixPE/PhoenixPE/wiki/PhoenixAPI PhoenixPE API].
+The great news is, that with PEBakery's user friendly and flexible scripting language and PhoenixPE's robust API, it's relatively easy to make your own scripts and include your favorite applications. Be sure to check out the [https://github.com/pebakery/pebakery-docs PEBakery Documentation] and the [https://github.com/PhoenixPE/PhoenixPE/wiki/PhoenixAPI PhoenixPE API].
 
 If you get stuck give a shout out in the forums, there is a good chance that somebody has made a script for a similar application or will be able to answer your questions.
 
-== Do I internet access in order to build PhoenixPE? ==
+== Do I need internet access in order to build PhoenixPE? ==
 
-Yes and No. In order to keep download sizes reasonable and provide the most up-to-date software PhoenixPE needs to download some tools the first time it is run. Depending on the scripts you select, setup files for the applications may also need to be downloaded. 
-Once application setup files are downloaded they are cached and will not be downloaded again unless you manually clear the cache, nuke the project, or elect to always download the latest version of a particular program.
+Yes and No. In order to comply with Microsoft's software license/distribution requirements PhoenixPE needs to download some tools from the Windows Automated Deployment Kit (WAIK) the first time it is run. Depending on the scripts you select, setup files, language definitions, signatures, etc. for the applications may also need to be downloaded from the author's website, CDN, or an authorized mirror. 
+Once downloaded, the tools and application setup files are cached and will not be downloaded again unless you manually clear the cache, nuke the project, or elect to always download the latest version of a particular program.
 
-Once the initial build is complete and the cache is populated you no longer need internet access for subsequent builds.
+'''TL;DR: Once the initial build is complete and the cache is populated you no longer need internet access for subsequent builds.'''
 
 == What if I have slow internet or poor reliability? ==
 
 In addition to saving bandwidth, PhoenixPE's cache system was built with situations like this in mind.
 
-On each app script that needs to download files, you will find a download button on the top right.
-You can use this button to pre-download any scripts you wish to use. They will be cached in ''PhoenixPE\Workbench\PhoenixPE\Programs'' and used in subsequent builds. Programs downloaded during build time will also be cached in the same location and used in subsequent builds.
+On each app script that requires files to be downloaded from the internet you will find a download button on the top right.
+You can use this button to pre-download setup files for any scripts you wish to use. Programs will be cached in ''PhoenixPE\Workbench\PhoenixPE\Programs'' and used in subsequent builds. Programs downloaded during build time will also be cached in the same location and used in subsequent builds.
 
 Since PEBakery and PhoenixPE are fully portable, it is also possible to place the PhoenixPE install directory on a USB drive or portable hard drive, plug in at someplace with a faster/more reliable internet connection and launch PEBakery to pre-download the apps you need.
 
-As a last resort, you can also download an installer manually and place it in the correct cache folder, but you must know exactly which path and file name that the script will be looking for, so this is best left for expert users who fully understand how each script operates.
+As a last resort, you can also download an applications installer manually and place it in the correct cache folder. Be advised that you must know exactly which path and file name that the script will be looking for, so this is best left for expert users who fully understand how each script operates.
 
 == There is a new version of program '''''xyz.exe''''' available. Can I update the script myself? ==