tutorials/JButler-CRUD-Tutorial.md

@@ -1009,7 +1009,7 @@ The [JButler Base Project](https://gitlab.labes.inf.ufes.br/labes/jbutler-base-p
 
 Looking at the above code, you can see that although we are using a ready-to-use front-end because of the lack of designers, it's still quite complicated to build a decent Web page in our system! To do a good job here, a developer should be familiar with [PrimeFaces](https://www.primefaces.org/) components and [AdminFaces](https://github.com/adminfaces/) layouts. For that purpose, I suggest exploring the [PrimeFaces Demo](https://www.primefaces.org/showcase/) and the [AdminFaces Showcase](https://github.com/adminfaces/admin-showcase). The above code, by the way, is based on the [DataTable CRUD example in PrimeFaces Demo](https://www.primefaces.org/showcase/ui/data/datatable/crud.xhtml?jfwid=14d21).
 
-Also in the above code, notice that some of the internationalized messages refer not to `msgs` but to `msgsCore`, as JButler suggests that the functionalities of the system be separated in modules or subsystems, which is why we implemented the Java classes under `br.ufes.inf.labes.oldenburg.core` (we named our only subsystem _core_). We need to provide those messages under `msgsCore`, so we create the file `src/main/resources/br/ufes/inf/labes/oldenburg/core/view/messages.properties` with the following contents:
+Also in the above code, notice that some of the internationalized messages refer not to `msgs` but to `msgsCore`, as JButler suggests that the functionalities of the system be separated in modules or subsystems (see [JButler Architecture](docs/JButler-Architecture)), which is why we implemented the Java classes under `br.ufes.inf.labes.oldenburg.core` (we named our only subsystem _core_). We need to provide those messages under `msgsCore`, so create the file `src/main/resources/br/ufes/inf/labes/oldenburg/core/view/messages.properties` with the following contents:
 
 ```sh
 ##