faq: rework company support A

[web.git] / faq.txt

diff --git a/faq.txt b/faq.txt
index 0d3fb35076c7d955e5031dc26f9f04e9cc5cac51..21a65627a3ac032cfbe0323b464c0117210085be 100644 (file)
--- a/faq.txt
+++ b/faq.txt
@@ -9,7 +9,8 @@ LEDE mainly targets embedded devices capable of running Linux. In most cases wir
 
 == How do I upgrade from OpenWrt to LEDE?
 
-Use the same mechanisms as used to upgrade from one OpenWrt version to a more recent versions, sysupgrade for example. With sysupgrade even your configuration should be migrated.
+Migrating from OpenWrt to LEDE should work similar to upgrading from one OpenWrt release to another.
+Using the +sysupgrade+ command is the preferred approach as this will also attempt to preserve the system configuration.
 
 == Where is the LEDE Wiki?
 
@@ -17,7 +18,7 @@ This is work in progress.
 
 == Where is the Forum?
 
-Currently we have mailing lists, see /communication.html
+Currently we have mailing lists, see link:communication.html[Communication].
 
 == What happens to the OpenWrt package feed?
 
@@ -33,9 +34,11 @@ No, LEDE is not affiliated with any specific company or any industry organizatio
 
 == The company I work for uses LEDE and wants to support the project. What should we do?
 
-The best support is that you allow and encourage your employees to contribute the changes you did internally back to the LEDE project.
-If you are a chip vendor for example adding support for your chips to LEDE would be a nice.
-This way others can also benefit from your changes and you reduce your maintenance cost, because you need less patches when using more recent versions of LEDE.
+Companies can best support LEDE by upstreaming the required code to support their products,
+any platform support code, patch submissions or even just detailed specifications are most appreciated.
+
+Upstreaming product support also benefits the company in the long run as ongoing maintenance and
+porting effort decreases over time while the amount of internally required changes can be reduced.
 
 == Are there plans to license LEDE under a different License?
 
@@ -50,15 +53,15 @@ The release process should be better automatized and the release should be bette
 
 The build system and many LEDE components are licensed under the GNU General Public License Version 2. Some parts are licensed under different licenses, this is mostly the case for packages not created in LEDE or OpenWrt.
 
-== Who hold the copyright of LEDE code?
+== Who holds the copyright of LEDE code?
 
-The original authors of the code holds the copyright.
+The original authors of the code hold the copyright.
 
 == Is the LEDE project a registered legal entity?
 
-No, the LEDE project is not a registered legal entity. The OpenWrt project is also no registered legal entity, but OpenWrt is represented by the Software in the Public Interest (SPI).
+No, the LEDE project is not a registered legal entity. The OpenWrt project is also not a registered legal entity, but OpenWrt is represented by 'Software in the Public Interest' (SPI).
 
 == Is LEDE a registered trademark?
 
-No, LEDE is not a registered trademark, but OpenWrt is a registered trademark which is holden by the Software in the Public Interest (SPI) in the name of the OpenWrt project.
+No, LEDE is not a registered trademark, but OpenWrt is a registered trademark which is held by the Software in the Public Interest (SPI) in the name of the OpenWrt project.