Merge pull request #126 from chuckwagoncomputing/rusEFI-stylization

rusEFI stylization

Components/Shadow-Dash.md

@@ -1,4 +1,4 @@
-In order to use Shadow Dash with rusEfi, you would need to copy rusefi.ini file into .efiAnalytics\config\ecuDef folder on your Android device and rename it to 'unknown.ini'
+In order to use Shadow Dash with rusEFI, you would need to copy rusefi.ini file into .efiAnalytics\config\ecuDef folder on your Android device and rename it to 'unknown.ini'
 
 I've used ES File Explorer since Windows does not show hidden folders - and .efiAnalytics is a hidden folder. In ES File Explorer settings I have 'show hidden files' checkbox enabled. 
 

Dev/Dev-Console-Implementation.md

@@ -1,12 +1,12 @@
 ## human readable protocol
 
-A typical line in rusEfi human-readable protocol look like
+A typical line in rusEFI human-readable protocol look like
 
 `line:16:rpm,100,maf,3.3,`
 
 Here `line` is a magic prefix, `16` is the length of the payload, and the payload `rpm,100,maf,3.3,` is a comma separated list of keys and pairs, let's call this "a line of known length"
 
-As for sending commands to rusEfi, there are two options
+As for sending commands to rusEFI, there are two options
 
 a) plain unwrapped command, for example
 
@@ -16,7 +16,7 @@ b) a command with specified length (this case the firmware can validate the comm
 
 `sec!7!rpm 400<end of line>`
 
-Pretty much same was as with data coming from rusEfi, we have a prefix `sec` and `7` for the payload length.
+Pretty much same was as with data coming from rusEFI, we have a prefix `sec` and `7` for the payload length.
 TODO: unify `line` and sec `one` day?
 
 ## java classes

Dev/Dev-Status.md

@@ -409,7 +409,7 @@ Engine chart size
 [SPI settings](rusEFI-project-Controller#spi-settings)  
 (🔶): SPI communication configuration  
 
-[rusEfi Console Settings](rusEFI-project-Controller#rusefi-console-settings)  
+[rusEFI Console Settings](rusEFI-project-Controller#rusefi-console-settings)  
 (💚): rusEFI console configuration  
 
 [Connection](rusEFI-project-Controller#connection)  

Documentation-Workflow.md

@@ -9,7 +9,7 @@ For example, in order for user abelom to edit this page:
 
 1) abelom would start editing at https://github.com/rusefi/rusefi_documentation/blob/master/Documentation_Workflow.md which would automatically create a branch in https://github.com/abelom/rusefi_documentation fork
 2) Once changed are made, abelom would create a Pull Request
-3) Once that PR is merged into primary rusEfi modified content would appear as https://github.com/rusefi/rusefi_documentation/blob/master/Documentation_Workflow.md
+3) Once that PR is merged into primary rusEFI modified content would appear as https://github.com/rusefi/rusefi_documentation/blob/master/Documentation_Workflow.md
 4) Within the next 5 minutes automation would sync this page into wiki git and it would be available with nicer layout as https://github.com/rusefi/rusefi/wiki/Documentation_Workflow
 
 Same but in different terms:
@@ -29,9 +29,9 @@ Long story short, for images to work correctly both in the technical git and the
 
 (More details: 
 Please note that all .md files like https://github.com/rusefi/rusefi_documentation/blob/master/FAQ/HOWTO_quick_start.md are displayed without folder name like https://github.com/rusefi/rusefi/wiki/HOWTO_quick_start - which also means
-that you need full image path like ``FAQ/images/rusEfi_console/rusEfi_console_start_screen.png`` for the image to be rendered properly. This is one of the github wiki features which are a bit counter-intuitive to me.
+that you need full image path like ``FAQ/images/rusEFI_console/rusEFI_console_start_screen.png`` for the image to be rendered properly. This is one of the github wiki features which are a bit counter-intuitive to me.
 
 This also means that .md file names have to be unique for the whole.)
 
 **Q:** What sort of fancy options do we have?
-**A:** We can do collapsible sections & hints sections! See [cranking](Cranking) for an example.
+**A:** We can do collapsible sections & hints sections! See [cranking](Cranking) for an example.

FAQ/rusEFI-chat.md

@@ -1,8 +1,8 @@
 
-[rusEfi forum](https://rusefi.com/forum/) is the central meeting point for everything rusEfi but there are also:
+[rusEFI forum](https://rusefi.com/forum/) is the central meeting point for everything rusEFI but there are also:
 
 - Slack at https://rusefi.slack.com/ see https://rusefi.com/forum/viewtopic.php?t=1198
 
 - Russian-speaking Skype group channel - стукнитесь в arro239 в Скайпе, чтобы добавиться.
 
-- https://www.facebook.com/rusEfiECU/ 
+- https://www.facebook.com/rusEfiECU/ 

Fuel/Wide-Band-Sensors.md

@@ -3,7 +3,7 @@
 A reliable measurement of the AFR is vital for the tuner to be able to tune the engine and be sure that his changes to the fueling are correct. For this purpose we recommend one of the readily available aftermarket wideband gauges or controllers.
 A wide-band oxygen sensor is pretty much a must for what we are doing here. Bosch is the only manufacturer of these sensors I am aware of. The wide-band precision of the sensor is achieved by a relatively sophisticated magic which happens inside the sensor, that's why 5 or 6 wises and that's why the sensor requires it's own controller (brain). Since there are at least two kinds of sensors it's safer to buy a kit.
 
-As of April 2016 rusEfi does not have build-in WBO controller.
+As of April 2016 rusEFI does not have build-in WBO controller.
 
 Wide-band controllers range from $35.00 for http://www.14point7.com/products/slc-free ($85 with sensor) all the way to high-200 for kits with a gauge.
 

HOWTO/CAN-Sniffer.md

@@ -1,4 +1,4 @@
-## HOWTO use custom build of rusEfi for CAN bus sniffing
+## HOWTO use custom build of rusEFI for CAN bus sniffing
 
 In this HOWTO I will explain how to see raw CAN message flow with less than $30 in hardware & some free software.
 

HOWTO/Console.md

@@ -6,7 +6,7 @@
 
 You can sniff either trigger angles or MAP values. 
 
-Analog chart tab in java console is a very, very plain oscilloscope build into rusEfi firmware.
+Analog chart tab in java console is a very, very plain oscilloscope build into rusEFI firmware.
 
 Analog chart always displays the signal for a duration of one complete engine cycle.
 

HOWTO/Debug-Fields.md

@@ -1,4 +1,4 @@
-Debug fields is an advanced troubleshooting feature allowing one to monitor internal state of some rusEfi subsystems. In an ideal world we would be always saving all these data points, in reality we need to only save those while troubleshooting something specific.
+Debug fields is an advanced troubleshooting feature allowing one to monitor internal state of some rusEFI subsystems. In an ideal world we would be always saving all these data points, in reality we need to only save those while troubleshooting something specific.
 
 `set debug_mode CODE`
 

HOWTO/Debug-Mode.md

@@ -1,4 +1,4 @@
-Debug fields is an advanced troubleshooting feature allowing one to monitor the internal state of some rusEfi subsystems. 
+Debug fields is an advanced troubleshooting feature allowing one to monitor the internal state of some rusEFI subsystems. 
 
 In TunerStudio, select "Base Engine Settings -> Debug Mode" and use the gauges from "Debug" category.
 

HOWTO/Engine-Types.md

@@ -1,8 +1,8 @@
 Update 2017: things are much more settled these days, at least 6 months without an incompatible configuration format change.
 
-The best way to configure rusEfi according to your engine setup is via Tuner Studio - there are not many settings there, it should be to some expend self-explanatory. In case of any questions your best chance at the moment is to ask questions on the forum - there are still not enough walk-troughs and articles. 
+The best way to configure rusEFI according to your engine setup is via Tuner Studio - there are not many settings there, it should be to some expend self-explanatory. In case of any questions your best chance at the moment is to ask questions on the forum - there are still not enough walk-troughs and articles. 
 
-But rusEfi is still in the phase of active development: some parts of the code are still far from final, and new configuration parameters are being added every month. Because of that, the TunerStudio project definition is still pretty volatile. Volatile TunerStudio project definition means your settings could be lost next time you upgrade the firmware, because of that we need a way to keep default configurations for each setup in a more persistent way. This is the reason why we have...
+But rusEFI is still in the phase of active development: some parts of the code are still far from final, and new configuration parameters are being added every month. Because of that, the TunerStudio project definition is still pretty volatile. Volatile TunerStudio project definition means your settings could be lost next time you upgrade the firmware, because of that we need a way to keep default configurations for each setup in a more persistent way. This is the reason why we have...
 
 
 Engine Type concept: we have an array of default configurations for different engines defined [right in the source code](https://github.com/rusefi/rusefi/tree/master/firmware/config/engines). Which of the configurations is used is controlled by 'engine type' field which is persisted in the internal chip flash memory along with the rest of the configuration. So, in order to get your trigger decoding parameters and your fuel & injection control strategies activated, you need to invoke the 'set engine_type X' command as described [http://rusefi.com/forum/viewtopic.php?f=5&t=210#p4038 here].

HOWTO/FSIO.md

@@ -2,11 +2,11 @@
 
 ## The content below is mostly from 2018 and is in the process of being updated. This wiki article needs to be viewed as a work in progress at this time and may contain contradictory information.  
 
-Flexible Logic is the fanciest-schmanciest feature of rusEfi. Using the FSIO a user can quickly add a logical function directly into the program of the ECU. 
+Flexible Logic is the fanciest-schmanciest feature of rusEFI. Using the FSIO a user can quickly add a logical function directly into the program of the ECU. 
 
-Flexible Logic allows advanced users to get unprecedented level of configurability for custom outputs and engine control. rusEfi supports up to 16 flexible outputs, each of these could be either an on/off or PWM signal. In case of a PWM signal the frequency is defined in the configuration and the duty cycle is dynamically controlled by the evaluated expression.
+Flexible Logic allows advanced users to get unprecedented level of configurability for custom outputs and engine control. rusEFI supports up to 16 flexible outputs, each of these could be either an on/off or PWM signal. In case of a PWM signal the frequency is defined in the configuration and the duty cycle is dynamically controlled by the evaluated expression.
 
-For FSIO, rusEfi console provides a better user experience due to automated human to RPN conversion.
+For FSIO, rusEFI console provides a better user experience due to automated human to RPN conversion.
 
 ---
 

HOWTO/Feature-Requests-the-Feature-Bounty-Program.md

@@ -1,5 +1,5 @@
-The challenge of rusEfi as of 2020 is the fact that hardware is way ahead of software at this point. With just a few programmers and the complexity of the project, it would be a while until normal users would be benefiting from rusEfi because of the complexity and knowledge required.
+The challenge of rusEFI as of 2020 is the fact that hardware is way ahead of software at this point. With just a few programmers and the complexity of the project, it would be a while until normal users would be benefiting from rusEFI because of the complexity and knowledge required.
 
-But if for any reason you would prefer to use rusEfi and look for any specific feature, money can probably help you!
+But if for any reason you would prefer to use rusEFI and look for any specific feature, money can probably help you!
 
-See also https://rusefi.com/forum/viewtopic.php?f=5&t=1642
+See also https://rusefi.com/forum/viewtopic.php?f=5&t=1642

HOWTO/HOWTO-Get-Running.md

@@ -81,11 +81,11 @@ http://www.littelfuse.com/~/media/automotive/datasheets/fuses/passenger-car-and-
 Once connected you should test the wires. Especially the power wires like coil wires and injector wires. A poor connection with a slight resistance like .1 ohms can cause an electrical fire, which I'm sure you do not want. Once everything is connected measure both the voltage drop and current from the ECU connector, or where ever is applicably appropriate. Using your voltage and current readings, calculate the ohms, if it's above about .1 ohms fix the issue. Take note that .1 ohms at 1A is about .1watt that that connection will have to dissipate. If you have a 12 cyl, and 12 .1 ohm connections, the connector will have to dissipate 1.2 watts. 
 
 
-HOWTO start you engine with rusEfi for the first time
+HOWTO start you engine with rusEFI for the first time
 
 ### test outputs
 
-Both rusEfi console and TS allows you to test if rusEfi properly controls things like injectors (you would hear the clicks), cooling fan (you would hear it - if needed), fuel pump (you would usually hear it - if needed), ignition coil (that's challenging if you have a distributor)
+Both rusEFI console and TS allows you to test if rusEFI properly controls things like injectors (you would hear the clicks), cooling fan (you would hear it - if needed), fuel pump (you would usually hear it - if needed), ignition coil (that's challenging if you have a distributor)
 
 
 ## get tachometer showing correct cranking rpm
@@ -101,13 +101,13 @@ Assuming you have the hardware ready to spark we now need to find your TDC posit
 
 Set cranking advance angle to zero for now. Use a timing gun while cranking. We now need to try different values of Engine->Trigger->global trigger angle offset until we get spark at zero advance - that's because we might know the relation between TDC#1 and trigger signal. 
 
-On Engine Sniffer tab of rusEfi console TDC#1 is shown with the green vertical line.
+On Engine Sniffer tab of rusEFI console TDC#1 is shown with the green vertical line.
 
 ![Initial Cranking Parameters](Images/Initial_cranking_parameters.png)
 
 ## cranking parameters
 
-rusEfi has separate cranking control strategy for your first couple of engine revolutions - usually you want more fuel, different timing and simultaneous injection to start an engine.
+rusEFI has separate cranking control strategy for your first couple of engine revolutions - usually you want more fuel, different timing and simultaneous injection to start an engine.
 
 ![Cranking Dialog](Images/Cranking_dialog_jan_2017.png)
 
@@ -137,7 +137,7 @@ One plain MAF workk next step is running with proper MAP sensor calibration & fl
 There are three ways to produce similar logs - the intention is for these three to have same exact data.
 
 1. SD card logging
-2. rusEfi console logging
+2. rusEFI console logging
 3. TunerStudio logging
 
 See also https://svn.code.sf.net/p/rusefi/code/trunk/firmware/console/binary/tunerstudio_configuration.h

HOWTO/HOWTO-Miata-NB2-on-Proteus.md

@@ -29,7 +29,7 @@ Two 23 pins Ampseal extension connectors allows you to wire more functions like
 
 The board pin mapping for OEM connector follows the tab given in the Pinning section below.
 
-![Connector Face](Images/NB2_Miata_ECU_Connectors_Drawing_rusefi_harness.png)
+![Connector Face](Images/NB2_Miata_ECU_Connectors_Drawing_rusEFI_harness.png)
 
 For the extension connectors the pinnig is the following \:
 

HOWTO/HOWTO-ask-questions.md

@@ -17,7 +17,7 @@ If after that you still need direct help then please have a read of the informat
 
  1) In TunerStudio, Use "DataLogging">"Start Logging" menu item. Logs are written to Documents\TunerStudioProjects\NAMEOFYOURPROJECT\DataLogs folder.
 
- 2) With rusEfi console, simply grab the latest .msl file from "out" folder
+ 2) With rusEFI console, simply grab the latest .msl file from "out" folder
  
  
 ## HOWTO Ask Technical Questions 
@@ -35,4 +35,4 @@ An example of a question asked with helpful background information:
 https://rusefi.com/forum/viewtopic.php?f=3&t=1282&start=101
 
 
-![video](FAQ/images/fantastic-story-video-or-it-never-happened.jpg)
+![video](FAQ/images/fantastic-story-video-or-it-never-happened.jpg)

HOWTO/HOWTO-contribute-to-documentation.md

@@ -14,7 +14,7 @@ This would produce a [Pull request like this](https://github.com/rusefi/rusefi_d
 https://github.com/rusefi/rusefi/blob/master/firmware/tunerstudio/rusefi.input
 
 
-#### How to contribute to rusEfi TunerStudio project
+#### How to contribute to rusEFI TunerStudio project
 
 
 Same as above, fork https://github.com/rusefi/rusefi and edit your local copy of

HOWTO/HOWTO-contribute-to-firmware.md

@@ -1,4 +1,4 @@
-The majority of rusEfi code is written in very plain C++ ("C with classes"), with rusEfi console and some code generating
+The majority of rusEFI code is written in very plain C++ ("C with classes"), with rusEFI console and some code generating
 tools written in java.
 
 Most of the needs are within the C/C++ firmware and automated testing. 
@@ -15,7 +15,7 @@ Testing coverage open tickets: https://github.com/rusefi/rusefi/labels/automated
 
 All open tickets: https://github.com/rusefi/rusefi/issues
 
-See [Try It](Try-It) for how to work on rusEfi code with zero or minimal hardware.
+See [Try It](Try-It) for how to work on rusEFI code with zero or minimal hardware.
 
 [Click here for a Q&A on source code.](http://rusefi.com/forum/viewtopic.php?f=5&t=10)
 

HOWTO/HOWTO-electronic-throttle-body-configuration.md

@@ -51,7 +51,7 @@ https://www.youtube.com/watch?v=USU0nnekokA
 
 ### Start with autotune
 
-rusEfi has auto-tuning software that can help generate a starting point for your PID settings.
+rusEFI has auto-tuning software that can help generate a starting point for your PID settings.
 
 ### _Ensure the engine is off! Do not attempt to start the engine during this process!_
 
@@ -67,4 +67,4 @@ The pedal map allows you to configure how the electronic throttle's position res
 
 This table is really one to tune to taste, since it has no bearing on actual engine performance, only on the relationship between driver input and resulting throttle position.
 
-[//]: # "Matt Kennedy"
+[//]: # "Matt Kennedy"

HOWTO/HOWTO-help-rusEFI.md

@@ -7,7 +7,7 @@ The weakest point of rusEFI is lack of samples and success stories. As of Aug 20
 
 We also do not have much user feedback in general - we do not know how many rusEFI units are used regularly and what are users looking for (we know about launch control).
 
-Another weak point of rusEFI is documentation. If you've played with rusEfi for any time chances are you have help [improve the documentation.](HOWTO-contribute-to-documentation)
+Another weak point of rusEFI is documentation. If you've played with rusEFI for any time chances are you have help [improve the documentation.](HOWTO-contribute-to-documentation)
 
 
 We are also extremely short on software developers. [HOWTO contribute to firmware](HOWTO-contribute-to-firmware)
@@ -27,4 +27,4 @@ There are two ways to help financially:
 
 One-time or monthly https://tinyurl.com/paypal-rusefi  
 
-One-time or monthly [rusEfi Patreon](https://www.patreon.com/rusefi)   
+One-time or monthly [rusEFI Patreon](https://www.patreon.com/rusefi)   

HOWTO/HOWTO-quick-start.md

@@ -33,11 +33,11 @@
 
 * Another way to upload firmware is using a [DFU file](HOWTO-DFU)
 
-## rusEfi Console
+## rusEFI Console
 
 [Console](Console)
 
-We have rusEfi console which is a handy development and debugging tool. The dev console is written in java and it talks to the ECU firmware. The console allows firmware monitoring and configuration. Here are some pictures of what it looks like when it operating correctly. 
+We have rusEFI console which is a handy development and debugging tool. The dev console is written in java and it talks to the ECU firmware. The console allows firmware monitoring and configuration. Here are some pictures of what it looks like when it operating correctly. 
 
 ![Java Console](Images/java_console_1.png)
 ![Java Console](Images/java_console_2.png)
@@ -60,7 +60,7 @@ To get the console working follow the below procedure, which assumes you have lo
       [10572.797285] cdc_acm 5-1:1.0: ttyACM0: USB ACM device
       ```
      *  In this case, the newly plugged in USB is register to ttyACM0, which you can find on /dev/ttyACM0
-* If you don't already have the Dev Console, get it http://rusefi.com/build_server/rusefi_bundle.zip (part of the same bundle) Take note rusEfi dev console required java 1.7+
+* If you don't already have the Dev Console, get it http://rusefi.com/build_server/rusefi_bundle.zip (part of the same bundle) Take note rusEFI dev console required java 1.7+
 * When you launch the Dev Console, it will ask you to select which serial address it should use. However you can specify that when you launch it by specifying a command line parameter as noted below.
   * Windows
     `java -jar rusefi_console.jar COM15`
@@ -78,7 +78,7 @@ Update: there is also a lazier way to self-stimulate now, you would not need the
 At this point, the Dev Console should be up and running. Play around with it and see what you can learn. Also note, it as some functionality as noted below. 
 
 * If used together with the build-in position sensor emulator, the console allows some level of testing on the bench, without a real engine or any additional hardware. The most useful feature is the plain signal sniffer - both real inputs and generated signals can go into it and this is actually quite handy. Another useful feature is the text log.
-* You can use the console to invoke rusEfi commands and control the internal flow using the 'Messages Central' tab
+* You can use the console to invoke rusEFI commands and control the internal flow using the 'Messages Central' tab
 ![Messages Central](Images/messages_central.png)
 
 ## Tuner Studio
@@ -205,11 +205,11 @@ I'd like to try to connect to Tuner Studio and see what happens. I have a USB/TT
  `4073 Alive`
 
 
-This UART/real serial is just another way to connect either TunerStudio or rusEfi console to the firmware. By combining both microUsb virtual serial and TTL real serial one can connect to rusEfi with both TunerStudio and rusEfi console simultaneously.
+This UART/real serial is just another way to connect either TunerStudio or rusEFI console to the firmware. By combining both microUsb virtual serial and TTL real serial one can connect to rusEFI with both TunerStudio and rusEFI console simultaneously.
 
 See also [Tunerstudio Connectivity](Tunerstudio-Connectivity)
 
-## rusEfi firmware
+## rusEFI firmware
 
 [Trigger](Trigger)
 
@@ -248,10 +248,10 @@ Q: Low side, high side... Too complicated! Where do I hook my coils?!
 
 A: There is some variation between vehicles and components. Please use [rusEFI forums](https://rusefi.com/forum) for custom installation help!
 
-Q: I've made some changes in Tuner Studio & hit Burn. 'Need Burn' has appeared but the values are not there after rusEfi reset?
+Q: I've made some changes in Tuner Studio & hit Burn. 'Need Burn' has appeared but the values are not there after rusEFI reset?
 
-A: rusEfi does not write to internal flash memory while your engine is running. In order to really write the values into the permanent memory you would need to stop the engine (or disconnect your stimulator). Online tuning is not affected by this issue - you can still tune and the new values would be applied right away, they just would not be saved until you stop the engine.
+A: rusEFI does not write to internal flash memory while your engine is running. In order to really write the values into the permanent memory you would need to stop the engine (or disconnect your stimulator). Online tuning is not affected by this issue - you can still tune and the new values would be applied right away, they just would not be saved until you stop the engine.
 
 Q: I've remapped some analog inputs and outputs but nothing has changed, looks like the old pins are still used for output?
 
-A: For most of the pinout changes to be applied you need to reset rusEfi. Do not forget to stop the engine so that the new config is saved into internal memory!
+A: For most of the pinout changes to be applied you need to reset rusEFI. Do not forget to stop the engine so that the new config is saved into internal memory!

HOWTO/Hardware-Test-Mode.md

@@ -1,8 +1,8 @@
-rusEfi firmware has a **I/O hardware testing mode** feature - this comes handy if you've just soldered some I/O board like Frankenso.
+rusEFI firmware has a **I/O hardware testing mode** feature - this comes handy if you've just soldered some I/O board like Frankenso.
 
 In order to activate I/O testing board you need to ground pin PB0. (You can confirm the current pin associated with this feature using `showconfig` command.)
 
-Once PB0 is ground, you need to reset rusEfi. 
+Once PB0 is ground, you need to reset rusEFI. 
 Currently dev console is not supported - in I/O testing mode you need to connect to the firmware using some terminal application like putty or hyperterminal. (TODO: add dev console support, for now you need to use putty)
 
 Same as with normal mode, console uses micro USB port for the data flow by default.

HOWTO/Idle-Control.md

@@ -1,5 +1,5 @@
 
-rusEfi supports both solenoid-type IAC out of the box (well, with a fly-back diode - 1 or two wire) and [stepper motors](Stepper-Motor) (4 to six wires, add-on board from eBay required)
+rusEFI supports both solenoid-type IAC out of the box (well, with a fly-back diode - 1 or two wire) and [stepper motors](Stepper-Motor) (4 to six wires, add-on board from eBay required)
 
 
 By default Idle control is in 'manual' mode, while in manual mode you can control the idle valve with
@@ -9,7 +9,7 @@ command, where X should be between 1 and 100.
 In order to enable automatic idle control you would need `set_idle_enabled 1` command. Another command related to idle is `set idle_position X`, where X is desired idle speed
 
 
-In case of stepper idle valve, the position is a percent of the total stepper steps. On startup, rusEfi would move stepper all the way in in order order to find zero position.
+In case of stepper idle valve, the position is a percent of the total stepper steps. On startup, rusEFI would move stepper all the way in in order order to find zero position.
 
 In case of solenoid valve, the % is just the PWM of the control signal - it has nothing to do with the actual percentage of valve opening and you should not expect it to be linear.
 

HOWTO/Logging.md

@@ -1,6 +1,6 @@
 ## SD card logging
 
-rusEfi supports SD card logging. SD has to be formatted FAT16 or FAT32, up to 32Gb cards are known to work.
+rusEFI supports SD card logging. SD has to be formatted FAT16 or FAT32, up to 32Gb cards are known to work.
 
 ![Fat Format](Images/Gat_format.png
 
@@ -10,6 +10,6 @@ logs are being written at about 2 megabytes per hour, so the oldest 128Mb card w
 ![TunerStudio Logging](Images/Ts_logging.png)
 
 
-In rusEfi console `sdinfo` command could be used to query logging state.
+In rusEFI console `sdinfo` command could be used to query logging state.
 
 ![SD Info](Images/SD_info.png)

HOWTO/MSDroid.md

@@ -4,12 +4,12 @@ Then you need to save this file: https://svn.code.sf.net/p/rusefi/code/trunk/fir
 
 Move the rusefi.ini file you've just downloaded to MSDroid/ini folder (I've used https://play.google.com/store/apps/details?id=com.estrongs.android.pop for that)
 
-In order to connect msDroid to rusEfi you would need to tap 'App settings' and select the paired Bluetooth device. As of today, msDroid does not turn Bluetooth on automatically.
+In order to connect msDroid to rusEFI you would need to tap 'App settings' and select the paired Bluetooth device. As of today, msDroid does not turn Bluetooth on automatically.
 
 
 Current status: partial integration
-* List of rusEfi gauges YES
-* List of rusEfi menues YES
+* List of rusEFI gauges YES
+* List of rusEFI menues YES
 * Simple single-values parameters YES
 
 * Gauge values NO

HOWTO/Online.md

@@ -1,13 +1,13 @@
 
 # rusEFI Online
 
-[rusEFI online](https://rusefi.com/online/) is facilitating data flow within rusEfi open source engine management community.
+[rusEFI online](https://rusefi.com/online/) is facilitating data flow within rusEFI open source engine management community.
 
 - share your tune
 - checkout other's tunes
 
 
-See [HOWTO set rusEfi Online authentication token](HOWTO-set-rusEFI-Online-authentication-token)
+See [HOWTO set rusEFI Online authentication token](HOWTO-set-rusEFI-Online-authentication-token)
 
 See [HOWTO upload tune](HOWTO-upload-tune)
 
@@ -19,4 +19,4 @@ See [HOWTO Remote Tuning](https://github.com/rusefi/rusefi/wiki/HOWTO-Remote-Tun
 ![x](https://github.com/rusefi/web_backend/blob/master/documentation/rusEFI%20remote.png)
 
 
-For development details see https://github.com/rusefi/web_backend
+For development details see https://github.com/rusefi/web_backend

HOWTO/Pages-HOWTO.md

@@ -14,6 +14,6 @@
 * [Upload a tune](HOWTO-upload-tune)
 * [Remote tune](HOWTO-Remote-Tuning)
 * [Search the wiki](HOWTO-Search-on-rusEFI-wiki)
-* [Set rusEfi Online authentication token](HOWTO-set-rusEFI-Online-authentication-token)
+* [Set rusEFI Online authentication token](HOWTO-set-rusEFI-Online-authentication-token)
 
-</details>
+</details>

HOWTO/Pages-Software.md

@@ -18,7 +18,7 @@
 * [How To DFU](HOWTO-DFU)
 * [How To Update Firmware](HOWTO-Update-Firmware)
 * [How To Upload a Tune](HOWTO-upload-tune)
-* [rusEFI Bundle](HOWTO/rusEFI-bundle.md)
+* [rusEFI Bundle](rusEFI-bundle)
 
 </details>
 

HOWTO/Troubleshooting.md

@@ -1,4 +1,4 @@
-Over the years of developing rusEfi at least 20 of these stm32f4discovery boards were destroyed by just the primary developers. Sometimes we know we've shorted VCC to GND, sometimes the reasons are unknown. TODO: one day we would know more about it
+Over the years of developing rusEFI at least 20 of these stm32f4discovery boards were destroyed by just the primary developers. Sometimes we know we've shorted VCC to GND, sometimes the reasons are unknown. TODO: one day we would know more about it
 
 TODO: write down safest operation protocols.
 

HOWTO/Tunerstudio-Connectivity.md

@@ -24,7 +24,7 @@ you are expected to see a response like this:
 Q: I try to connect with Tuner Studio and it says "line:532:rusEfiVersion,20140822@4388 Ford
 Aspire,outpin,c1@PC6,outpin,c2@PA5,ou"?
 
-A: what you have is a piece of rusEfi own console text-based protocol, you need to connect TS to the other port.
+A: what you have is a piece of rusEFI own console text-based protocol, you need to connect TS to the other port.
 
 Q: how should it look in Tuner Studio mini terminal?
 

HOWTO/rusEFI-bundle.md

@@ -1,11 +1,11 @@
 
 
-`rusefi.bin` file is compiled rusEfi firmware. Sometimes you would have `rusefi_no_asserts.bin` variation of this file with fewer safety checks.
+`rusefi.bin` file is compiled rusEFI firmware. Sometimes you would have `rusefi_no_asserts.bin` variation of this file with fewer safety checks.
 
- `rusefi.dfu` is also compiled rusEfi firmware, that file is used for DFU mode of flashing.
+ `rusefi.dfu` is also compiled rusEFI firmware, that file is used for DFU mode of flashing.
 
  
- `rusefi.ini` is TunerStudio project template file, you would use it if you use TunerStudio software to tune your rusEfi unit.
+ `rusefi.ini` is TunerStudio project template file, you would use it if you use TunerStudio software to tune your rusEFI unit.
  See http://www.tunerstudio.com/index.php/downloads for TunerStudio download
  
- See http://rusefi.com and https://github.com/rusefi/rusefi_documentation for more information about rusEfi
+ See http://rusefi.com and https://github.com/rusefi/rusefi_documentation for more information about rusEFI

Hardware/Frankenso/Hardware-Frankenso.md

@@ -15,7 +15,7 @@ Frankenso should be powered by ignition switch. Frankenso main relay output can
 
 [For sale fully assembled!](https://www.tindie.com/products/russian/frankenso-full-bundle/)
 
-See [HOWTO Quick Start](HOWTO-quick-start) for rusEfi Quick Start.
+See [HOWTO Quick Start](HOWTO-quick-start) for rusEFI Quick Start.
 
 [Known Issues](https://raw.githubusercontent.com/rusefi/rusefi/master/hardware/frankenso/known_issues.txt)
 

Hardware/Hardware.md

@@ -8,11 +8,11 @@ As of March 2020 Frankenso board is sold as mostly as a DIY kit.
 | Board | Features | Connectors/Misc. Info | Released in | Maximum recommended engine |
 | ----- | -------- | --------------------- | ----------- | ---------------------------|
 | [Frankenso](Hardware-Frankenso) | + Most customizable board<br/>+ larger 154x152mm 4-layer board requires a Medium Box shipping rate<br/>+ on-board power supply<br/>+ 20x4 LCD screen<br/>+ joystick<br/>+ works both with external brain boards and on-board stm32 chip<br/>+ knock sensor chip<br/>+ used Denso OEM cases available | on-board 64 pin connector<br/>SD card, USB/TTL, CAN<br/>open source hardware | 2014 | Flexible - probably 8 cylinder max recommended |
-| [Prometheus](https://rusefi.com/forum/viewtopic.php?f=4&t=1215)  | + The only rusEfi board with on-board wide band controller.<br/>+ compact 4-layer PCB smaller than 93 x 100 mm<br/>+ on-board power supply<br/>+ knock sensor chip<br/>+ stepper motor IAC controller chip<br/>+ stepper motor IAC controller chip<br/>+ onboard 4-channel "smart" protected ignition drivers<br/>+ bluetooth module<br/>+ supports two packages of on-board stm32 chips | no on-board connector (wired)<br/>SD card, USB/TTL, CAN  | 2017 | 4 cylinder. No plans to offer assembled units. |
-| [Frankenstein](https://rusefi.com/forum/viewtopic.php?f=4&t=359)  | + Simplest rusEfi board<br/>+ our smaller two-layer board<br/>+ Small Box shipping rate<br/>+ low price<br/>- external 5v power supply required<br/>- external brain board required | no on-board connector (wired)<br/>SD card, USB/TTL, CAN<br/>open source hardware | 2014 | Flexible - probably 8 cylinder max recommended. No plans to offer assembled units. |
+| [Prometheus](https://rusefi.com/forum/viewtopic.php?f=4&t=1215)  | + The only rusEFI board with on-board wide band controller.<br/>+ compact 4-layer PCB smaller than 93 x 100 mm<br/>+ on-board power supply<br/>+ knock sensor chip<br/>+ stepper motor IAC controller chip<br/>+ stepper motor IAC controller chip<br/>+ onboard 4-channel "smart" protected ignition drivers<br/>+ bluetooth module<br/>+ supports two packages of on-board stm32 chips | no on-board connector (wired)<br/>SD card, USB/TTL, CAN  | 2017 | 4 cylinder. No plans to offer assembled units. |
+| [Frankenstein](https://rusefi.com/forum/viewtopic.php?f=4&t=359)  | + Simplest rusEFI board<br/>+ our smaller two-layer board<br/>+ Small Box shipping rate<br/>+ low price<br/>- external 5v power supply required<br/>- external brain board required | no on-board connector (wired)<br/>SD card, USB/TTL, CAN<br/>open source hardware | 2014 | Flexible - probably 8 cylinder max recommended. No plans to offer assembled units. |
 | [microRusEfi](Hardware-microRusEFI) | + Available fully assembled!<br/>+ about 10 analog inputs<br/>+ One VR/Hall input channel for crank sensor<br/>+ One Hall input channel for crank sensor<br/>+ 4 injector output channels<br/>+ 4 logic level coil control channels (external igniters could be needed for some coils) | 48-pin connector<br/>On-board DBW<br/>USB, CAN<br/>open source hardware  | 2019 | 4 cylinder, single electronic throttle |
 | [Hellen](https://rusefi.com/forum/viewtopic.php?f=4&t=1682) | Coming soon! | modular design| 2020 | TBD cylinder, single electronic throttle |
-| [Proteus](Proteus) | + rusEfi if you have lots of hardware or cylinders<br/>+ 4 layer PCB, 135mm x 82.5mm<br/>+ 16 low-side outputs, limited to 3 amps each (injectors, relays, check engine light, etc)<br/>+ 12x ignition outputs (or general purpose 5v, 100mA push-pull)<br/>+ Dual electronic throttles<br/>+ 4x High-side 12v drivers, 1 amp each<br/>+ 4 thermistor analog inputs (2.7k pull up resistor)<br/>+ 12 General purpose analog inputs<br/>+ Dual VR sensors (crank position, wheel speed)<br/>+ 6 digital inputs (hall cam/crank position, wheel speed, clutch/brake switch, etc) | TE Ampseal connectors: 2x 35 pin, 1x 23 pin<br/>rusEfi's most fully-featured shield<br/>IP68 waterproof case | 2020 | 12 cylinder, dual electronic throttles |
+| [Proteus](Proteus) | + rusEFI if you have lots of hardware or cylinders<br/>+ 4 layer PCB, 135mm x 82.5mm<br/>+ 16 low-side outputs, limited to 3 amps each (injectors, relays, check engine light, etc)<br/>+ 12x ignition outputs (or general purpose 5v, 100mA push-pull)<br/>+ Dual electronic throttles<br/>+ 4x High-side 12v drivers, 1 amp each<br/>+ 4 thermistor analog inputs (2.7k pull up resistor)<br/>+ 12 General purpose analog inputs<br/>+ Dual VR sensors (crank position, wheel speed)<br/>+ 6 digital inputs (hall cam/crank position, wheel speed, clutch/brake switch, etc) | TE Ampseal connectors: 2x 35 pin, 1x 23 pin<br/>rusEFI's most fully-featured shield<br/>IP68 waterproof case | 2020 | 12 cylinder, dual electronic throttles |
 
 
 ### Q: How to select a board?

Hardware/Pages-Hardware.md

@@ -34,7 +34,7 @@
 * [MRE Kit instructions](Hardware-microRusEFI-kit-instructions)
 * [MRE Hardware checks](Hardware-microRusEFI-hardware-checks)
 * [MRE DIY TLDR](microRusEFI-DIY-TLDR)
-* [MRE Connectors](Hardware-microRusEfi-connectors)
+* [MRE Connectors](Hardware-microRusEFI-connectors)
 
 </details>
 
@@ -42,7 +42,7 @@
 <details><summary><u>PNP Boards</u></summary>
 
 * [PNP 48 - MRE based for Miata NA](microrusefi48adapter.pdf)
-* [PNP 72 - MRE based for Miata NB2](Hardware/pnp_microRusEfi_nb2/hw72nb.pdf)
+* [PNP 72 - MRE based for Miata NB2](Hardware/pnp_microRusEFI_nb2/hw72nb.pdf)
 * PNP 88 - Proteus based for 88pin Bosch - Coming Soon
 * [MRE Adapter 48](MREAdapter48)
 * [MRE Adapter 55](MREAdapter55)

Hardware/microRusEFI/Hardware-microRusEFI-hardware-checks.md

@@ -8,4 +8,4 @@ v0.1/v0.2 power supply check list
 1. 5v test pad: expected 5.0v
 
 
-![front lower](Hardware/microrusefi/Hardware_microRusEfi_0_2_top_checks.jpg)
+![front lower](Hardware/microRusEFI/Hardware_microRusEFI_0_2_top_checks.jpg)

Hardware/microRusEFI/Hardware-microRusEFI-kit-instructions.md

@@ -32,10 +32,10 @@ For component placement please use interactive BOM
 [0.4.7](https://rusefi.com/docs/ibom/microRusEfi_R0.4.7.html)
 
 
-[Some checkpoints](Hardware/microrusefi/Hardware_microRusEfi_0_4_7_front_checks.jpg)
+[Some checkpoints](Hardware/microRusEFI/Hardware_microRusEFI_0_4_7_front_checks.jpg)
 
 
-All microRusEfi kits use [MRE F4 rusEfi firmware - DOWNLOAD LATEST BUNDLE HERE](https://rusefi.com/build_server/rusefi_bundle_mre_f4.zip)
+All microRusEfi kits use [MRE F4 rusEFI firmware - DOWNLOAD LATEST BUNDLE HERE](https://rusefi.com/build_server/rusefi_bundle_mre_f4.zip)
 
 
 
@@ -49,9 +49,9 @@ All microRusEfi kits use [MRE F4 rusEfi firmware - DOWNLOAD LATEST BUNDLE HERE](
 [0.4.7 schematics PDF](https://github.com/rusefi/hw_microRusEfi/blob/master/microRusEfi_Schematic_0_4_7.pdf)
 
 
-[rusEfi Slack channel](https://rusefi.com/forum/viewtopic.php?f=13&t=1198) is the primary support channel.
+[rusEFI Slack channel](https://rusefi.com/forum/viewtopic.php?f=13&t=1198) is the primary support channel.
 
-[HOWTO program rusEfi using DFU](HOWTO-DFU)
+[HOWTO program rusEFI using DFU](HOWTO-DFU)
 
 # Crankshaft position sensor options: Hall or VR
 
@@ -62,10 +62,10 @@ Depending on your crankshaft position sensor type you would need to populate eit
 0.4.8: Comes set for VR (R9 & C12 are now on the front since)
 
 VR mode front - comes pre-assembled
-![Back](Hardware/microrusefi/Hardware_microRusEfi_0.4.7_vr_front.png)
+![Back](Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_vr_front.png)
 
 VR mode back
-![Back](Hardware/microrusefi/Hardware_microRusEfi_0.4.7_vr_back.jpg)
+![Back](Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_vr_back.jpg)
 
 
 0.4.5, 0.4.7: For Hall, you would need to REMOVE R15 & C35 on the front, and install R17=1.5K R18=R19=4.7K on the back.
@@ -73,36 +73,36 @@ VR mode back
 0.4.8: For Hall, you would need to REMOVE R15&R9, C12 & C35 on the front, and install R17=1.5K R18=R19=4.7K on the back.
 
 0.5.0 Hall
-![Front](Hardware/microrusefi/Hardware_microRusEfi_0.5.0_hall_mode.jpg)
+![Front](Hardware/microRusEFI/Hardware_microRusEFI_0.5.0_hall_mode.jpg)
 
 0.4.7 Hall mode front
-![Front](Hardware/microrusefi/Hardware_microRusEfi_0.4.7_hall_front.jpg)
+![Front](Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_hall_front.jpg)
 
 0.4.7 Hall mode back
-![Back](Hardware/microrusefi/Hardware_microRusEfi_0.4.7_hall_back.png)
+![Back](Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_hall_back.png)
 
 
 
 # Board Photos
 
-![F](Hardware/microrusefi/Hardware_microRusEfi_0.5.3_assembled_front.jpg)
+![F](Hardware/microRusEFI/Hardware_microRusEFI_0.5.3_assembled_front.jpg)
 
-![F](Hardware/microrusefi/Hardware_microRusEfi_0.5.0_module_assembled_front.jpg)
+![F](Hardware/microRusEFI/Hardware_microRusEFI_0.5.0_module_assembled_front.jpg)
 
 
 Kit front:
 
-![Front](Hardware/microrusefi/Hardware_microRusEfi_0.4.7_pre_assembled_front.jpg)
+![Front](Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_pre_assembled_front.jpg)
 
 Kit parts on the front:
 
-![Front](Hardware/microrusefi/Hardware_microRusEfi_0.4.7_kit_front.jpg)
+![Front](Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_kit_front.jpg)
 
 Kit parts on the back:
-![Back](Hardware/microrusefi/Hardware_microRusEfi_0.4.7_kit_assembled_back.jpg)
+![Back](Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_kit_assembled_back.jpg)
 
 Flyback diodes orientation
-![Back](Hardware/microrusefi/Hardware_microRusEfi_0.4.7_kit_diodes_orientation.jpg)
+![Back](Hardware/microRusEFI/Hardware_microRusEFI_0.4.7_kit_diodes_orientation.jpg)
 
 
 # Important details
@@ -127,7 +127,7 @@ J7 header in bottom-left corner of microRusEFI allows direct SWD programming usi
 
 Tag Connect In circuit Cable "NO Legs" Version
 
-![x](Hardware/microrusefi/TC2030_SWD.jpg)
+![x](Hardware/microRusEFI/TC2030_SWD.jpg)
 
 ### Note - Missing wire caps  
-In the even of a missing wire cap on the molex plug the correct part number is 64320-1301 and these can be easily sourced online  
+In the even of a missing wire cap on the molex plug the correct part number is 64320-1301 and these can be easily sourced online  

Hardware/microRusEFI/Hardware-microRusEFI-wiring.md

@@ -2,15 +2,15 @@
 
 [Interactive Pinout](https://rusefi.com/docs/pinouts/microrusefi/)
 
-![connector](Hardware/microrusefi/Hardware_microRusEfi_connector.png)
+![connector](Hardware/microRusEFI/Hardware_microRusEFI_connector.png)
 
-![microRusEfi photo](Hardware/microrusefi/Hardware_microRusEfi_connector.jpg)
+![microRusEfi photo](Hardware/microRusEFI/Hardware_microRusEFI_connector.jpg)
 
 Rear side of PCB
 
-![microRusEfi image](Hardware/microrusefi/Hardware_microRusEfi_0_3_PCB_pinout.png)
+![microRusEfi image](Hardware/microRusEFI/Hardware_microRusEFI_0_3_PCB_pinout.png)
 
-![x](Hardware/microrusefi/microRusEfi_connectors/MRE_reality.jpg)
+![x](Hardware/microRusEFI/microRusEFI_connectors/MRE_reality.jpg)
 
 In some cases without "main relay output +12v" both pins #1 and #5 should be connected to the single source of +12v.
 
@@ -18,7 +18,7 @@ Pin #1 feeds ETB H-bridge, battery voltage sense, gp5 & gp6 high-side +12v, TLE8
 
 # Pin Types
 
-These tables provide technical information about the different types of pin found on microrusEfi.
+These tables provide technical information about the different types of pin found on microRusEFI.
 
 ## Power
 
@@ -91,8 +91,8 @@ R12=10K
 R13=0R
 
 
-![front hall](Hardware/microrusefi/Hardware_microRusEfi_0_1_assembled_front_hall_setup.jpg)
-![front lower](Hardware/microrusefi/Hardware_microRusEfi_0_1_assembled_front_lower.jpg)
+![front hall](Hardware/microRusEFI/Hardware_microRusEFI_0_1_assembled_front_hall_setup.jpg)
+![front lower](Hardware/microRusEFI/Hardware_microRusEFI_0_1_assembled_front_lower.jpg)
 
 
 
@@ -102,7 +102,7 @@ microRusEFI exposes the following pins in addition to the primary 48 pin connect
 
 J4:
 
-![x](Hardware/microrusefi/J4.png)
+![x](Hardware/microRusEFI/J4.png)
 | N | Name | Possible functions (not all listed!) |
 |----|-------------| ---- |
 | 9 | GNS | GND
@@ -131,7 +131,7 @@ Three GPIOs are available on J2 (SWD) connector. If you are not going to use deb
 
 For HW version 0.5.0 and newer some additional GPIOs are available on testpoints around STM32.
 
-![x](Hardware/microrusefi/J8_9_10.png)
+![x](Hardware/microRusEFI/J8_9_10.png)
 
 [Testpoint Interactive Pinout](https://rusefi.com/docs/pinouts/microrusefi/pads.html)
 

Hardware/microRusEFI/microRusEFI-Manual.md

@@ -15,21 +15,21 @@
 
 ## HOWTO update microRusEFI Firmware
 
-The best way to update microRusEfi firmware is using rusEfi console "Auto DFU" mode. 
+The best way to update microRusEfi firmware is using rusEFI console "Auto DFU" mode. 
 In AutoDFU a few things happen once you click the "Update Firmware" button.
 
 0) AutoDFU procedure works if your Windows device manager shows "STMicroelectronics Virtual COM Port" in "Ports" category.
 
 ![img](Support/AutoDFU_precondition.png)
 
-1) rusEfi console finds your microRusEFI device serial port and sends it a command to reboot into DFU mode.
+1) rusEFI console finds your microRusEFI device serial port and sends it a command to reboot into DFU mode.
 
 It is expected that microRusEFI would stop blinking the blue light and reboot. It is expected that Virtual COM Port
 would disappear from Device Manager and "STM Device in DFU Mode" device would appear in "Universal Serial Bus controllers" category.
 
 ![img](Support/stm_device_in_dfu_mode.png)
    
-2) rusEfi console gives Windows 3 seconds to re-enumerate USB device from Virtual COM Port to DFU Device.
+2) rusEFI console gives Windows 3 seconds to re-enumerate USB device from Virtual COM Port to DFU Device.
 
 Now the programming begins and the expected output is along the following lines:
 ```
@@ -117,8 +117,8 @@ Done!
 Please power cycle device to exit DFU mode
 ```
 
-At this point you need to power rusEfi device off/on and new firmware version would be running!
+At this point you need to power rusEFI device off/on and new firmware version would be running!
 
-New firmware version could be confirmed in rusEfi window title - both console and firmware versions are displayed there.
+New firmware version could be confirmed in rusEFI window title - both console and firmware versions are displayed there.
 
 ![img](Support/console_showing_firmware_version.png)

Hardware/microRusEFI/microRusEFI_connectors/Hardware-microRusEFI-connectors.md

@@ -6,13 +6,13 @@ US: 2007+ Nissan Altima & 2007+ Nissan Sentra
 Harness side socket.
 "Removable front key" style.
 Left from China, Right removed from Nissan Sentra.
-![i](Hardware/microrusefi/microRusEfi_connectors/microRusEfi_removable_key_China_and_Nissan_harness_socket.jpg)
+![i](Hardware/microRusEFI/microRusEFI_connectors/microRusEFI_removable_key_China_and_Nissan_harness_socket.jpg)
 
 
 Removed from Nissan Sentra - square terminals.
 Left large terminal. Right small pin terminal.
 
-![i](Hardware/microrusefi/microRusEfi_connectors/microRusEfi_Nissan_crimped_terminals.jpg)
+![i](Hardware/microRusEFI/microRusEFI_connectors/microRusEFI_Nissan_crimped_terminals.jpg)
 
 
 PCB side: [Molex 48 pin PCB plug](https://www.mouser.com/datasheet/2/276/5007620481_PCB_HEADERS-179151.pdf) 5007620481 500762-0481
@@ -37,7 +37,7 @@ todo
 
 
 "Side clip" style harness socket, both from China.
-![i](Hardware/microrusefi/microRusEfi_connectors/microRusEfi_side_clip_China_harness_socket.jpg)
+![i](Hardware/microRusEFI/microRusEFI_connectors/microRusEFI_side_clip_China_harness_socket.jpg)
 
 
 Terminals
@@ -54,7 +54,7 @@ With a utility knife you need to cut 4 keys from inside the male part to mate de
 as is.
 
 
-![i](Hardware/microrusefi/microRusEfi_connectors/microRusEfi_helping_black_plug_with_brown.jpg)
+![i](Hardware/microRusEFI/microRusEFI_connectors/microRusEFI_helping_black_plug_with_brown.jpg)
 
 
-![i](Hardware/microrusefi/microRusEfi_connectors/microRusEfi_lada_donor_harness.jpg)
+![i](Hardware/microRusEFI/microRusEFI_connectors/microRusEFI_lada_donor_harness.jpg)