Skip to content

Commit 255bd8a

Browse files
authored
Fix indenting
1 parent 66c250f commit 255bd8a

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

docs/edgetxsupport.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -12,29 +12,29 @@ If you are a radio manufacturer and are interested in using EdgeTX as the firmwa
1212

1313
1. **Develop the support of your hardware yourself and get it merged to EdgeTX code base**
1414

15-
- Make the needed changes to support your hardware yourself, submit a pull request to the EdgeTX team for review. If approved, your changes will be merged into the main branch of EdgeTX where it will be published and distributed as part of the normal release schedule.
15+
* Make the needed changes to support your hardware yourself, submit a pull request to the EdgeTX team for review. If approved, your changes will be merged into the main branch of EdgeTX where it will be published and distributed as part of the normal release schedule.
1616

17-
- The new radio will be added to our list of supported radios after the merge.
17+
* The new radio will be added to our list of supported radios after the merge.
1818

19-
- Future development of new features and bug fixes will include all the supported radios for consideration.
19+
* Future development of new features and bug fixes will include all the supported radios for consideration.
2020

21-
- Manufacturers are highly encouraged to participate in testing, and bugs fixing to ensure our continuous development will not break the firmware of your radios.
21+
* Manufacturers are highly encouraged to participate in testing, and bugs fixing to ensure our continuous development will not break the firmware of your radios.
2222

23-
- If you do not have the know-how or resources to make the needed changes to support your hardware yourself, then you can contact the EdgeTX Team to get some assistance to give you some references, or try to outsource the development to third party who understand the EdgeTX code base.
23+
* If you do not have the know-how or resources to make the needed changes to support your hardware yourself, then you can contact the EdgeTX Team to get some assistance to give you some references, or try to outsource the development to third party who understand the EdgeTX code base.
2424

2525
2. **Co-develop the hardware and firmware with EdgeTX Team**
2626

27-
- If your radio introduces novel features (e.g., a new hardware platform and/or new hardware capabilities) and you managed to draw the interest from one or more EdgeTX team members, co-development may be viable. Try reach out via [Discord](https://discord.gg/wF9wUKnZ6H) or via email at psc@edgetx.org for your proposal.
27+
* If your radio introduces novel features (e.g., a new hardware platform and/or new hardware capabilities) and you managed to draw the interest from one or more EdgeTX team members, co-development may be viable. Try reach out via [Discord](https://discord.gg/wF9wUKnZ6H) or via email at psc@edgetx.org for your proposal.
2828

29-
- ***Note**: EdgeTX is developed by volunteers, and while innovative hardware often attracts attention, progress depends on contributors’ availability. Manufacturers concerned about timelines should allocate internal resources to accelerate development.*
29+
* ***Note**: EdgeTX is developed by volunteers, and while innovative hardware often attracts attention, progress depends on contributors’ availability. Manufacturers concerned about timelines should allocate internal resources to accelerate development.*
3030

3131
3. **Develop and Maintain your own fork of EdgeTX**
3232

33-
- Create your own fork of EdgeTX and implement hardware-specific modifications independently. (Please ensure the fork remains publicly available)
33+
* Create your own fork of EdgeTX and implement hardware-specific modifications independently. (Please ensure the fork remains publicly available)
3434

35-
- ***In this case, your team assumes full responsibility for long-term maintenance and bug fixes.***
35+
* ***In this case, your team assumes full responsibility for long-term maintenance and bug fixes.***
3636

37-
- ***Note**: To avoid user confusion, **always label** your software as a "custom branch of EdgeTX vx.x.x" (**never** "EdgeTX"). Commercial use of the EdgeTX logo is strictly prohibited.*
37+
* ***Note**: To avoid user confusion, **always label** your software as a "custom branch of EdgeTX vx.x.x" (**never** "EdgeTX"). Commercial use of the EdgeTX logo is strictly prohibited.*
3838

3939
We strongly encourage all manufacturers planning to produce EdgeTX-compatible radio transmitters to contact the EdgeTX Project Steering Committee (PSC) early for collaboration. This allows our experts to advise on optimizing your product for EdgeTX compatibility.
4040

0 commit comments

Comments
 (0)