Update badge references

doc/development/licensed_feature_availability.md

@@ -4,7 +4,7 @@ group: License
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
 ---
 
-# Licensed feature availability **(STARTER)**
+# Licensed feature availability
 
 As of GitLab 9.4, we've been supporting a simplified version of licensed
 feature availability checks via `ee/app/models/license.rb`, both for
@@ -17,9 +17,9 @@ feature such as [Related issues](../user/project/issues/related_issues.md) or
 [Service Desk](../user/project/service_desk.md),
 it should be restricted on namespace scope.
 
-1. Add the feature symbol on `EES_FEATURES`, `EEP_FEATURES` or `EEU_FEATURES` constants in
-  `ee/app/models/license.rb`. Note on `ee/app/models/ee/namespace.rb` that _Bronze_ GitLab.com
-  features maps to on-premise _EES_, _Silver/Premium_ to _EEP_ and _Gold/Ultimate_ to _EEU_.
+1. Add the feature symbol on `EES_FEATURES`, `EEP_FEATURES`, or `EEU_FEATURES` constants in
+  `ee/app/models/license.rb`. Note that the prefix `EES` signifies Starter, `EEP` signifies
+  Premium, and `EEU` signifies Ultimate.
 1. Check using:
 
 ```ruby
@@ -35,7 +35,7 @@ the instance license.
 
 1. Add the feature symbol on `EES_FEATURES`, `EEP_FEATURES` or `EEU_FEATURES` constants in
   `ee/app/models/license.rb`.
-1. Add the same feature symbol to `GLOBAL_FEATURES`
+1. Add the same feature symbol to `GLOBAL_FEATURES`.
 1. Check using:
 
 ```ruby