one more thing no ammend

src/gateway/understanding-kong/glossary.md

@@ -25,7 +25,6 @@ title: Glossary
 |Route| A route, also referred to as a route object, defines rules to match client requests to upstream services. Each route is associated with a service, and a service may have multiple routes associated with it. routes are entry points to upstream services.|
 |Service| A service, also referred to as a service object, is the upstream APIs and microservices that Kong manages. For example, Services could be a data transformation microservice or a billing API. The main attribute of a Service is its URL, the destination where Kong proxies traffic. The URL can be set as a single string, or by specifying its protocol, host, port, and path.  |
 |Super admin| A super admin, or any role with read and write access to the /admins and /rbac endpoints, creates new Roles and customize permissions. A super admin can invite and disable other admin accounts, assign and revoke roles to admins, create new roles with custom permissions, and create new workspaces.|
-|Service configuration| The concrete configuration that a runtime group can be configured with in order to expose the service version’s functionality. At the onset, the only type of implementation that we will support will be a Kong proxy.|
 |Spec| A service version can have an optional spec (e.g. OAPI spec for a RESTful service) associated with it.    |
 |Tags| Tags are customer-defined labels that let you manage, search for, and filter core entities using the ?tags querystring parameter. Tags can be added when creating or editing most core entities. Each tag must be composed of one or more alphanumeric characters,` \_\`, `-`, . or `~`. |
 |Teams| Teams organize developers into working groups.|