Fixed links in index.md

Author: ko1N

src/index.md

@@ -10,10 +10,10 @@ memflow is a library that allows live memory introspection of running systems an
 
 The very core of the library is a [PhysicalMemory](https://docs.rs/memflow/latest/memflow/mem/phys_mem/trait.PhysicalMemory.html) that provides direct memory access in an abstract environment. This object that can be defined both statically, and dynamically with the use of the `inventory` feature. If `inventory` is enabled, it is possible to dynamically load libraries that provide Direct Memory Access.
 
-Through the use of OS abstraction layers, like [memflow-win32](https://github.com/memflow/memflow/tree/master/memflow-win32), user can gain access to virtual memory of individual processes, by creating objects that implement [MemoryView](https://docs.rs/memflow/latest/memflow/mem/memory_view/trait.MemoryView.html).
+Through the use of OS abstraction layers, like [memflow-win32](https://github.com/memflow/memflow-win32), user can gain access to virtual memory of individual processes, by creating objects that implement [MemoryView](https://docs.rs/memflow/latest/memflow/mem/memory_view/trait.MemoryView.html).
 
 Bridging the two is done by a highly throughput optimized virtual address translation function, which allows for crazy fast memory transfers at scale.
 
 The core is architecture independent (as long as addresses fit in 64-bits), and currently both 32, and 64-bit versions of the x86 family are available to be used.
 
-For non-rust libraries, it is possible to use the [FFI](https://github.com/memflow/memflow/tree/master/memflow-ffi) to interface with the library.
+For non-rust libraries, it is possible to use the [FFI](https://github.com/memflow/memflow/tree/main/memflow-ffi) to interface with the library.