replace relative links with absolute ones in docs to be usable in wiki

Author: bygu4

README.md

@@ -1,14 +1,14 @@
 # LZ4 Scatter-Gather (SG) Buffers Support in Linux Kernel block layer
 
-This project extends the LZ4 compression algorithm implementation in the Linux kernel to support SG-buffers (based on `struct bio_vec`), 
+This project extends the LZ4 compression algorithm implementation in the Linux kernel to support SG-buffers (based on `struct bio_vec`),
 eliminating the need for additional data copying.
 
 ## Key Features
 
 - Kernel-space implementation of LZ4 with SG buffers support
 - Block device module for tests and experiments
 - Test environment for validation
-- API extension in `lz4e/include/lz4e.h`
+- API extension in [`lz4e/include/lz4e.h`](https://github.com/ItIsMrLaG/lz4-sgori/blob/main/lz4e/include/lz4e.h)
 
 ## Extended API
 

doc/API.md

@@ -100,4 +100,4 @@ For I/O, iterators can be created and modified before calling the function and a
 runtime to contain current position after the function is called.
 Compression requires additional 1KB of working memory on top of existing 16KB, the exact size is in macro `LZ4E_MEM_COMPRESS`.
 
-Described signatures and macros can be found at [lz4e.h](../lz4e/include/lz4e.h).
+Described signatures and macros can be found at [lz4e.h](https://github.com/ItIsMrLaG/lz4-sgori/blob/main/lz4e/include/lz4e.h).

doc/Usage.md

@@ -78,11 +78,12 @@ inserted into your kernel. After that, to be able to access exported symbols you
 See more details: <https://docs.kernel.org/kbuild/modules.html#symbols-from-another-external-module>.
 
 As examples for both cases, you can see how the block dev module is compiled when running `make` and `make bdev`:
-- [top-module Kbuild](../Kbuild);
-- [setting KBUILD_EXTRA_SYMBOLS](../lz4e_bdev/Kbuild).
+- [top-module Kbuild](https://github.com/ItIsMrLaG/lz4-sgori/blob/main/Kbuild);
+- [setting KBUILD_EXTRA_SYMBOLS](https://github.com/ItIsMrLaG/lz4-sgori/blob/main/lz4e_bdev/Kbuild).
 
-After the symbols can be accessed by your module, to use functions provided by the header [`lz4e.h`](../lz4e/include/lz4e.h) you can add it to your includes
-using gcc's `-I` flag, or by directly copying it into your sources.
+After the symbols can be accessed by your module, to use functions provided by the header
+[`lz4e.h`](https://github.com/ItIsMrLaG/lz4-sgori/blob/main/lz4e/include/lz4e.h)
+you can add it to your includes using gcc's `-I` flag, or by directly copying it into your sources.
 
 ## Using the block device