docs: fix build, add 'translation context' term to glossary

docs/conf.py

@@ -13,7 +13,7 @@
 # out serve to show the default value.
 
 import sys, os, datetime
-import pkg_resources
+from importlib import metadata
 import pylons_sphinx_themes
 
 # General configuration
@@ -41,7 +41,7 @@
 # other places throughout the built documents.
 #
 # The short X.Y version.
-version = pkg_resources.get_distribution('translationstring').version
+version = metadata.version('translationstring')
 # The full version, including alpha/beta/rc tags.
 release = version
 

docs/glossary.rst

@@ -21,13 +21,19 @@ Glossary
      predefines a :term:`translation domain`.
 
    Translation Domain
-     A string representing the "context" in which a particular
+     A string representing the "domain" in which a particular
      translation was made.  For example the word "java" might be
      translated differently if the translation domain is
      "programming-languages" than would be if the translation domain
      was "coffee".  Every :term:`translation string` has an associated
      translation domain.
 
+   Translation Context
+     An optional string added to help resolve translation ambiguities
+     associated with very short terms, such as those which appear in
+     GUI menus, etc.  See:
+     https://www.gnu.org/software/gettext/manual/gettext.html#Contexts
+
    Message Identifier
      An unchanging string that is the identifier for a particular
      translation string.  For example, you may have a translation