fix broken links

julelang · Aug 9, 2023 · 259b75d · 259b75d
1 parent 6f9391f
commit 259b75d
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/src/compiler/compiling/using-backend-compiler.md b/src/compiler/compiling/using-backend-compiler.md
@@ -5,4 +5,4 @@ JuleC will automatically choose the recommended C++ compiler when compiling your
 
 If you need a special configuration for your build, it is recommended to create a script file for it or write compile command in a document such as a readme files. This makes it clearer and easier how to compile the project, as well as a faster and more comfortable development experience.
 
-Please read [backend](/compiler/backend) documentations for more information about supported C++ compilers and standards.
+Please read [backend](/compiler/backend/) documentations for more information about supported C++ compilers and standards.
diff --git a/src/getting-started/install-from-source/compile-from-ir.md b/src/getting-started/install-from-source/compile-from-ir.md
@@ -14,7 +14,7 @@ You need the Jule source codes to compile the IR code. IR codes have dependencie
 
 The include directories of the IR codes are set to be in the root directory of the Jule source code of the IR code. So put your IR code inside the root directory of Jule source tree you got and build in that directory. If you want a different directory, you need to change the include directories of IR.
 
-Of course you need a C++ compiler to compile the IR code. At this point it is recommended to use one of the officially supported compilers. You can check [relavant manual page](/compiler/backend) for more details.
+Of course you need a C++ compiler to compile the IR code. At this point it is recommended to use one of the officially supported compilers. You can check [relavant manual page](/compiler/backend/) for more details.
 
 We recommend compiling JuleC's IR codes with Clang and C++17. The recommended build command below is built accordingly. You can change the optimization level as you wish. -O0 is recommended for debugging. If you're using it to get the most up-to-date compiler in the main branch, you can still use -O0 to get the fastest build time, but it may also result in a JuleC build with a higher transpilation time. But in the general scenario you wait less time than you would expect for the -O3 optimization level.