Modify licensing article [HC-1570] (#390)

Removed notes about contact

Author: gorillagripcore

content/About Arduino/Trademarks & Licensing/Licensing-for-products-based-on-Arduino.md

@@ -20,9 +20,6 @@ If you’re designing your own board based on the open-source Arduino designs, t
 
 * Your derived board must be open-source hardware, thus full bill of materials and CAD files shall be made public (not just the schematics). Such files shall be licensed with the same license as the one used by us (that is CC-BY-SA-4.0 in most cases).
 
-  > [!NOTE]
-  > If you want to release your derived board without making it open-source hardware, contact us at **[email protected]** to get an exception to this rule.
-
 * Do not use the “Arduino” trademark in your design files or on the product itself as this would be a trademark infringement and may suggest that your board is made or approved by Arduino.
 
 * When using unmodified original hardware manufactured by Arduino inside a third-party product (as part of a kit or pre-mounted in a larger assembly), no restrictions apply. Mentioning Arduino on the product or its documentation or commercial assets is not required; if you intend on doing so, see the [trademark policy](https://www.arduino.cc/en/trademark) to make sure you comply with the trademark regulation.
@@ -51,16 +48,10 @@ In this case you need to go through three steps:
 
 1. The first thing to do is to check whether you're using any code snippet or library covered by the GNU General Public License (GPL). Unfortunately, in that case you are mandated to disclose the source code of the entire project. To avoid this you'll need to replace that code or library with another one that is made available under a more permissive license such as LGPL, MIT, BSD, Apache-2.0, or MPL-2.0. As an alternative, you can contact the author(s) and ask for a commercial license.
 
-   > [!NOTE]
-   > If you need a commercial license for official libraries developed by Arduino licensed under the GNU GPL, contact us at **[email protected]**.
-
 2. Prepare a comprehensive document with the list of all the open source components involved, along with the copyright notices and the licenses, and make it available to the end users as part of the documentation.
 
 3. Last but not least, you need to comply with article 4.d of the LGPL license which has specific and very technical requirements. Complying with such requirements, which derive from the LGPL being used in the Arduino core, is usually a matter of providing end users with some documentation and binary files.
 
-   > [!NOTE]
-   > We can provide companies with support and tools that allow them to comply with this requirement in an easy and automated way. Contact us at **[email protected]** for more information.
-
 ### Distributing a modified version of an Arduino core or library without disclosing its source code
 
 In this case you need to check the license of the specific code part that you modified. If that code was licensed under LGPL, GPL, or MPL-2.0 you must keep your modifications open source. If a permissive license such as MIT, BSD, or Apache-2.0 is used, you are not mandated to keep your modifications open source but you must retain the copyright notices of the original codebase.
@@ -71,15 +62,12 @@ If you intend to make the Arduino IDE, CLI, or Cloud-CLI available to your users
 
 If you intend to include the CLI in your project and call it as a library (instead of calling it as an executable binary), its GPLv3 license will apply to your code as well which results in the obligation to keep the entire codebase open source.
 
-> [!NOTE]
-> If you still need to call the CLI as a library in your derived product without having to release the combined work as open source, contact us at **[email protected]** to get an exception to this rule.
-
 If you intend to distribute the IDE or CLI _with modifications_, you must keep your modifications open source. Also, you cannot use the "Arduino" trademark in the name of the resulting artifact.
 
 ---
 
 ## Still need help?
 
-If the licensing terms are too restrictive for your project, or if you need further help, contact us at **[email protected]** to explore possible licensing options.
+If you need further help, contact us at **[email protected]**
 
 <!-- markdownlint-disable-file HC001 -->