Browse Source

feat: Links corrected

Vaclav Elias 2 years ago
parent
commit
221c54f0eb
2 changed files with 4 additions and 4 deletions
  1. 3 3
      en/contributors/engine/architecture/build-details.md
  2. 1 1
      en/contributors/toc.yml

+ 3 - 3
en/contributors/engine/architecture/build-details.md

@@ -1,8 +1,8 @@
-# Build details
+# Build details
 This is a technical description what happens in our build and how it is organized. This covers mostly the build architecture of Stride itself.
 This is a technical description what happens in our build and how it is organized. This covers mostly the build architecture of Stride itself.
 
 
 * [Targets](../Targets) contains the MSBuild target files used by Games
 * [Targets](../Targets) contains the MSBuild target files used by Games
-* [sources/common/targets](../sources/common/targets) (generic) and [sources/targets](../sources/targets) (Stride-specific) contains the MSBuild target files used to build Stride itself.
+* [sources/common/targets](../sources/common/targets) (generic) and [sources/targets](https://github.com/stride3d/stride/tree/master/sources/targets) (Stride-specific) contains the MSBuild target files used to build Stride itself.
 
 
 Since 3.1, we switched from our custom build system to the new csproj system with one nuget package per assembly.
 Since 3.1, we switched from our custom build system to the new csproj system with one nuget package per assembly.
 
 
@@ -18,7 +18,7 @@ Also, we use `RuntimeIdentifiers` to select graphics platform. [MSBuild.Sdk.Extr
 
 
 Since we want to package tools (i.e. GameStudio, ConnectionRouter, CompilerApp) with a package that contains only the executable with proper dependencies to other NuGet runtime packages, we use NuGet API to resolve assemblies at runtime.
 Since we want to package tools (i.e. GameStudio, ConnectionRouter, CompilerApp) with a package that contains only the executable with proper dependencies to other NuGet runtime packages, we use NuGet API to resolve assemblies at runtime.
 
 
-The code responsible for this is located in [Stride.NuGetResolver](../../../sources/shared/Stride.NuGetResolver).
+The code responsible for this is located in [Stride.NuGetResolver](https://github.com/stride3d/stride/tree/master/sources/shared/Stride.NuGetResolver).
 
 
 Later, we might want to take advantage of .NET Core dependency resolving to do that natively. Also, we might want to use actual project information/dependencies to resolve to different runtime assemblies and better support plugins.
 Later, we might want to take advantage of .NET Core dependency resolving to do that natively. Also, we might want to use actual project information/dependencies to resolve to different runtime assemblies and better support plugins.
 
 

+ 1 - 1
en/contributors/toc.yml

@@ -37,7 +37,7 @@ items:
     - name: Dependency graph
     - name: Dependency graph
       href: engine/architecture/dependency-graph.md
       href: engine/architecture/dependency-graph.md
     - name: Asset introspection
     - name: Asset introspection
-      href: engine/architecture/asset-introspection.html
+      href: engine/architecture/asset-introspection.md
 - name: 🎓 Contribute to the documentation
 - name: 🎓 Contribute to the documentation
   expanded: false
   expanded: false
   href: documentation/index.md
   href: documentation/index.md