Fix minor typos (#62)

- managment -> management
- SourgeForce -> SourceForge
- ther -> their

Author: bact

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" >}}

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" >}}

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 <http://schema.org>, but CodeMeta provides a few additional terms not found in <http://schema.org> which may be helpful for software projects.  CodeMeta also restricts the context to use only those <https://schema.org> 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 <http://schema.org>, but CodeMeta provides a few additional terms not found in <http://schema.org> which may be helpful for software projects.  CodeMeta also restricts the context to use only those <https://schema.org> 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.