From 70737d9ecd09966a238aff88ab68d11966a3d1f4 Mon Sep 17 00:00:00 2001 From: Tom van Woudenberg Date: Tue, 25 Feb 2025 08:43:04 +0100 Subject: [PATCH] typo --- book/installation-and-setup/versioning_changelog.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/installation-and-setup/versioning_changelog.md b/book/installation-and-setup/versioning_changelog.md index 3be6d74..d6c69be 100644 --- a/book/installation-and-setup/versioning_changelog.md +++ b/book/installation-and-setup/versioning_changelog.md @@ -1,6 +1,6 @@ # TeachBooks versioning with changelog -Versions combined with a changelog can be a very effective way to communicate book changes to the reader and allow reuse of specific versions. We recommend [TeachBooks versioning]((../features/versioning.md)), which comes in two flavors: +Versions combined with a changelog can be a very effective way to communicate book changes to the reader and allow reuse of specific versions. We recommend [TeachBooks versioning](../features/versioning.md), which comes in two flavors: 1. `academic_year.additions.errata` versioning for books tailed-made for courses in which content is added / adapted during the course and might be restructured extensively every year while remaining to be available in the original form. An example can be seen in [the source repository of the Engineering Systems Optimization book](https://github.com/TUDelft-books/CME4501/tags) showing tags for different versions. 2. `major.errata` versioning for books which are more stable over years, in which big changes are covered only by the version number.