From c0f542f6cb87a60d3a1805925601a573e05b158c Mon Sep 17 00:00:00 2001 From: Arthit Suriyawongkul Date: Thu, 18 Sep 2025 03:14:41 +0100 Subject: [PATCH 1/3] Fix minor typos - managment -> management - SourgeForce -> SourceForge - ther -> their Signed-off-by: Arthit Suriyawongkul --- content/crosswalk/debian.md | 2 +- content/crosswalk/trove.md | 2 +- content/user-guide.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/content/crosswalk/debian.md b/content/crosswalk/debian.md index 407048f..152a9dd 100644 --- a/content/crosswalk/debian.md +++ b/content/crosswalk/debian.md @@ -5,6 +5,6 @@ date: "2017-06-01" --- -The [Debian package system](https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_archive_meta_data) defines archive metadata that is used by the popular `apt` package managment system on Debian and Ubuntu Linux distributions. +The [Debian package system](https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_archive_meta_data) defines archive metadata that is used by the popular `apt` package management system on Debian and Ubuntu Linux distributions. {{< crosswalk name="Debian Package" >}} diff --git a/content/crosswalk/trove.md b/content/crosswalk/trove.md index e81ac6d..3c31dcb 100644 --- a/content/crosswalk/trove.md +++ b/content/crosswalk/trove.md @@ -3,7 +3,7 @@ title: "Crosswalk for Trove Software Map" image: "/img/sourceforge.png" --- -[Trove Software Map](https://sourceforge.net/p/easyhtml5/tracinst/Software%20Map%20and%20Trove/#what-is-trove). Trove is the system used by SourgeForce.net to classify software projects. +[Trove Software Map](https://sourceforge.net/p/easyhtml5/tracinst/Software%20Map%20and%20Trove/#what-is-trove). Trove is the system used by SourceForge.net to classify software projects. {{< crosswalk name="Trove Software Map" >}} diff --git a/content/user-guide.md b/content/user-guide.md index c6590a5..ad02d60 100644 --- a/content/user-guide.md +++ b/content/user-guide.md @@ -203,7 +203,7 @@ because in the latter, `"https://cran.r-project.org"` is the `"url"` of `rmarkdo ## The context -Every CodeMeta document must refer to the context file *codemeta.jsonld*, for example via a URL. This indicates that all terms in the document should be interpreted in the "context" of CodeMeta. Most terms are chosen to match the equivalent terms in , but CodeMeta provides a few additional terms not found in which may be helpful for software projects. CodeMeta also restricts the context to use only those terms that are explicitly listed on ther [terms](/terms/) page. Users wanting to include additional terms must extend the context (see [developer-guide](/developer-guide/)). +Every CodeMeta document must refer to the context file *codemeta.jsonld*, for example via a URL. This indicates that all terms in the document should be interpreted in the "context" of CodeMeta. Most terms are chosen to match the equivalent terms in , but CodeMeta provides a few additional terms not found in which may be helpful for software projects. CodeMeta also restricts the context to use only those terms that are explicitly listed on their [terms](/terms/) page. Users wanting to include additional terms must extend the context (see [developer-guide](/developer-guide/)). The context file may be modified and updated in the future, if new JSON properties are added or existing ones modified. From 6454690c9f992822c501af805d99de7c493d89f3 Mon Sep 17 00:00:00 2001 From: Arthit Suriyawongkul Date: Wed, 1 Oct 2025 08:10:05 +0100 Subject: [PATCH 2/3] their -> the --- content/user-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/user-guide.md b/content/user-guide.md index ad02d60..118d8d1 100644 --- a/content/user-guide.md +++ b/content/user-guide.md @@ -203,7 +203,7 @@ because in the latter, `"https://cran.r-project.org"` is the `"url"` of `rmarkdo ## The context -Every CodeMeta document must refer to the context file *codemeta.jsonld*, for example via a URL. This indicates that all terms in the document should be interpreted in the "context" of CodeMeta. Most terms are chosen to match the equivalent terms in , but CodeMeta provides a few additional terms not found in which may be helpful for software projects. CodeMeta also restricts the context to use only those terms that are explicitly listed on their [terms](/terms/) page. Users wanting to include additional terms must extend the context (see [developer-guide](/developer-guide/)). +Every CodeMeta document must refer to the context file *codemeta.jsonld*, for example via a URL. This indicates that all terms in the document should be interpreted in the "context" of CodeMeta. Most terms are chosen to match the equivalent terms in , but CodeMeta provides a few additional terms not found in which may be helpful for software projects. CodeMeta also restricts the context to use only those terms that are explicitly listed on the [terms](/terms/) page. Users wanting to include additional terms must extend the context (see [developer-guide](/developer-guide/)). The context file may be modified and updated in the future, if new JSON properties are added or existing ones modified. From 3a7d426484eccaacd2d9a82680d6993bc42122cb Mon Sep 17 00:00:00 2001 From: Arthit Suriyawongkul Date: Wed, 1 Oct 2025 08:17:32 +0100 Subject: [PATCH 3/3] Remove trailing space --- content/user-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/user-guide.md b/content/user-guide.md index 118d8d1..204b12c 100644 --- a/content/user-guide.md +++ b/content/user-guide.md @@ -203,7 +203,7 @@ because in the latter, `"https://cran.r-project.org"` is the `"url"` of `rmarkdo ## The context -Every CodeMeta document must refer to the context file *codemeta.jsonld*, for example via a URL. This indicates that all terms in the document should be interpreted in the "context" of CodeMeta. Most terms are chosen to match the equivalent terms in , but CodeMeta provides a few additional terms not found in which may be helpful for software projects. CodeMeta also restricts the context to use only those terms that are explicitly listed on the [terms](/terms/) page. Users wanting to include additional terms must extend the context (see [developer-guide](/developer-guide/)). +Every CodeMeta document must refer to the context file *codemeta.jsonld*, for example via a URL. This indicates that all terms in the document should be interpreted in the "context" of CodeMeta. Most terms are chosen to match the equivalent terms in , but CodeMeta provides a few additional terms not found in which may be helpful for software projects. CodeMeta also restricts the context to use only those terms that are explicitly listed on the [terms](/terms/) page. Users wanting to include additional terms must extend the context (see [developer-guide](/developer-guide/)). The context file may be modified and updated in the future, if new JSON properties are added or existing ones modified.