Glossary.md

@@ -3,7 +3,7 @@ This page lists key concepts and terminology related to the PEP system, and prov
 | Concept | Abbreviation | Description |
 | ------- | ------------ | ----------- |
 | Access Administrator | AA | The PEP role responsible for [data access management](Access-control#data-access) and [assignment of users to access groups](Access-control#role-determination). Users with this role are called "access administrators". Not to be confused with the "Acccess Manager" service. |
-| access group | | A named group of users that can be [authorized](Access-control) for specific actions. Also called a "role" in the system. |
+| access group  <a name="access_group"></a> | | A named group of users that can be [authorized](Access-control) for specific actions. Also called a "role" in the system. |
 | Access Manager | AM | The PEP service responsible for [data access authorization](Access-control#data-access). AM cooperates with the Transcryptor (TS) service to issue data access [tickets](Access-control#tickets). Not to be confused with the "Access Administrator" role. |
 | Application Programming Interface | API | The set of (primitive) operations that a software system provides. Raw API operations are intended for use from programming languages, allowing programs to be written that provide users with a simpler and/or more expressive level of interaction with the system. |
 | [authorization](Access-control#authorization) | | Determining whether a user is allowed to perform certain actions in a software system. |