From 00053b6df6a4f49a6b5eabc2305757c06971915d Mon Sep 17 00:00:00 2001
From: rusefillc <48498823+rusefillc@users.noreply.github.com>
Date: Thu, 20 Jan 2022 15:18:33 -0500
Subject: [PATCH] Updated rusEFI calibration via CAN (markdown)

---
 rusEFI-calibration-via-CAN.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/rusEFI-calibration-via-CAN.md b/rusEFI-calibration-via-CAN.md
index b01d9e2b..6b417aa1 100644
--- a/rusEFI-calibration-via-CAN.md
+++ b/rusEFI-calibration-via-CAN.md
@@ -2,7 +2,9 @@
 
 With all the electromagnetic interference around the gasoline engine due to sparking CAN physical layer provides the level of reliability above RS232 and USB physical layers.
 
-[ISO 15765-2](PDFs/ISO-15765-2-2004.pdf), or ISO-TP (Transport Layer), helps us exchange up to 4096 packets into which we wrap TS protocol. See also [wikipedia](https://en.wikipedia.org/wiki/ISO_15765-2) https://github.com/rusefi/rusefi/tree/master/java_console/io/src/main/java/com/rusefi/io/can folder has java implementation of ISO-TP packet encoding/decoding.
+[ISO 15765-2](PDFs/ISO-15765-2-2004.pdf), or ISO-TP (Transport Layer), helps us exchange up to 4096 packets into which we wrap TS protocol. See also [wikipedia](https://en.wikipedia.org/wiki/ISO_15765-2)
+
+https://github.com/rusefi/rusefi/tree/master/java_console/io/src/main/java/com/rusefi/io/can folder has java implementation of ISO-TP packet encoding/decoding.
 
 There is no standard way of communicating with CAN bus on Windows. At the moment rusEFI is focusing on [PCAN by Peak System](https://www.peak-system.com/) and ELM327 options of the Windows side of CAN.