More typos

docs/administration/admin.md

@@ -4,4 +4,4 @@ Whether you have set up your own instance of Gramps Web or signed up for a pre-i
 
 The focus of this section is on administrative tasks performed by **tree owners**. Usually, there is one tree owner for each family tree database (although as tree owner, you can also create other tree owner accounts).
 
-This section only deals with actions that can be performed from the web interface. For command line tools or server configuration, see the previous section [Setup](setup.md).
+This section only deals with actions that can be performed from the web interface. For command line tools or server configuration, see the previous section [Setup](../install_setup/setup.md).

docs/development/dev.md

@@ -7,8 +7,8 @@ hide:
 
 Gramps Web is a web application that consists of two components that are developed separately:
 
-- **Gramps Web API** is a RESTful API written in Python and based on Flask. The source code is hosted at [github.com/gramps-project/gramps-web-api](https://github.com/gramps-project/gramps-web-api/). It manages database access and genealogical functions directly leveraging the Gramps Python library. It serves as the backend of Gramps Web. For development documentation, see [Backend](dev-backend/index.md).
-- **Gramps Web Frontend** is a Javascript web application that serves as the frontend to Gramps Web. The source code is hosted at [github.com/gramps-project/gramps-web](https://github.com/gramps-project/gramps-web/). For development documentation, see [Frontend](dev-frontend/index.md).
+- **Gramps Web API** is a RESTful API written in Python and based on Flask. The source code is hosted at [github.com/gramps-project/gramps-web-api](https://github.com/gramps-project/gramps-web-api/). It manages database access and genealogical functions directly leveraging the Gramps Python library. It serves as the backend of Gramps Web. For development documentation, see [Backend](backend/index.md).
+- **Gramps Web Frontend** is a Javascript web application that serves as the frontend to Gramps Web. The source code is hosted at [github.com/gramps-project/gramps-web](https://github.com/gramps-project/gramps-web/). For development documentation, see [Frontend](frontend/index.md).
 
 A note on versioning: Gramps Web API and and the Gramps Web frontend are versioned independently. At present, "Gramps Web" – the combined application – does not have a separate version number. Both projects adhere to [SemVer](https://semver.org/).
 

docs/user-guide/blog.md

@@ -6,7 +6,7 @@ In the Gramps database, blog posts are represented as sources with a note attach
 
 ## Add a blog post
 
-To add a blog post, you can use Gramps Web or Gramps Dekstop ([synchronized](sync.md) with Gramps Web), the steps are the same in both cases:
+To add a blog post, you can use Gramps Web or Gramps Dekstop ([synchronized](../administration/sync.md) with Gramps Web), the steps are the same in both cases:
 
 - Add a new source. The title of the source will be the title of your blog post, the author of the source will be the author of the post.
 - Optionally, associate the source with a repository corresponding to your Gramps Web blog

docs/user-guide/registration.md

@@ -25,6 +25,6 @@ If the confirmation e-mail does not arrive (and you have checked your Spam folde
 
 ## 4. Enable account
 
-After the e-mail address has been confirmed, the tree owner will receive an e-mail notification and can enable the new user account by going to the "User administration" section in settings page (accessible via the user icon in the top app bar) and changing the user role from "disabled" to any of the [other roles](../Users.md).
+After the e-mail address has been confirmed, the tree owner will receive an e-mail notification and can enable the new user account by going to the "User administration" section in settings page (accessible via the user icon in the top app bar) and changing the user role from "disabled" to any of the [other roles](../install_setup/users.md).
 
 Note that the new user will *not* receive an automated notification that their account has been enabled, so it is advisible for the administrator to notify them personally.