From e345c28eec3ae28fa3d2eff8e3030895c2782567 Mon Sep 17 00:00:00 2001 From: SusanQuigley Date: Thu, 16 Jul 2020 19:00:29 +0000 Subject: [PATCH] Update 'translate/file-formats/02.md' Fixed link --- translate/file-formats/02.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/translate/file-formats/02.md b/translate/file-formats/02.md index e36f359..8cc1385 100644 --- a/translate/file-formats/02.md +++ b/translate/file-formats/02.md @@ -36,6 +36,6 @@ The easiest way to get content marked up with USFM is by using an editor that is When contemplating which software to use, please keep in mind that translation is not just about words; there are many technical aspects that need to be taken into consideration. Whatever software is used, just remember that Bible translations need to be written using USFM markers. -To see some common USFM markers, please read [USFM Markers]. +To see some common USFM markers, please read [Common Markers for Formatting Scripture](../translate/format-markers/01.md). To read more about USFM notation, please read http://paratext.org/about/usfm . \ No newline at end of file