Fix links

src/registrar/assets/sass/_theme/_admin.scss

@@ -685,18 +685,7 @@ div.dja__model-description{
 
     p, li {
         font-size: medium;
-    }
-
-    @media (prefers-color-scheme: light) {
-        p, li {
-            color: var(--body-fg);
-        }
-    }
-
-    @media (prefers-color-scheme: dark) {
-        p, li {
-            color: var(--secondary);
-        }
+        color: var(--secondary);
     }
 
     li {
@@ -704,7 +693,7 @@ div.dja__model-description{
         font-family: Source Sans Pro Web,Helvetica Neue,Helvetica,Roboto,Arial,sans-serif;
     }
 
-    a {
+    a, a:link, a:visited {
         font-size: medium;
         color: #005288 !important;
     }

src/registrar/templates/django/admin/includes/descriptions/contact_description.html

@@ -2,7 +2,7 @@
 Contacts include anyone who has access to the registrar (known as “users”) and anyone listed in a domain request, 
 including other employees and authorizing officials. 
 Only contacts who have access to the registrar will have 
-a corresponding record within the <a class="usa-button usa-button--unstyled text-underline" href="{% url 'admin:registrar_user_changelist' %}">Users</a> table.
+a corresponding record within the <a class="text-underline" href="{% url 'admin:registrar_user_changelist' %}">Users</a> table.
 </p>
 
 <p>

src/registrar/templates/django/admin/includes/descriptions/domain_information_description.html

@@ -2,7 +2,7 @@
 Domain information represents the basic metadata for an approved domain and the organization that manages it. 
 It does not include any information specific to the registry (DNS name servers, security email). 
 Registry-related information 
-can be managed within the <a class="usa-button usa-button--unstyled text-underline" href="{% url 'admin:registrar_domain_changelist' %}">Domains</a> table.
+can be managed within the <a class="text-underline" href="{% url 'admin:registrar_domain_changelist' %}">Domains</a> table.
 </p>
 
 <p>
@@ -10,7 +10,7 @@ Updating values here will immediately update the corresponding values that users
 </p>
 
 <p>
-Domain information is similar to <a class="usa-button usa-button--unstyled text-underline" href="{% url 'admin:registrar_domainrequest_changelist' %}">Domain requests</a>, 
+Domain information is similar to <a class="text-underline" href="{% url 'admin:registrar_domainrequest_changelist' %}">Domain requests</a>, 
 and the fields are nearly identical, 
 but edits made to one are not made to the other. 
 Domain information exists so we don’t modify details of an approved request after adjudication 

src/registrar/templates/django/admin/includes/descriptions/domain_invitation_description.html

@@ -11,6 +11,6 @@ A “received” status indicates that the recipient has logged in.
 
 <p>
 If an invitation is created in this table, an email will not be sent. 
-To have an email sent, go to the domain in <a class="usa-button usa-button--unstyled text-underline" href="{% url 'admin:registrar_domain_changelist' %}">Domains</a>, 
+To have an email sent, go to the domain in <a class="text-underline" href="{% url 'admin:registrar_domain_changelist' %}">Domains</a>, 
 click the “Manage domain” button, and add a domain manager. 
 </p>

src/registrar/templates/django/admin/includes/descriptions/domain_request_description.html

@@ -6,6 +6,6 @@ Updating values here will immediately update the corresponding values that users
 <p>
 Once a domain request has been adjudicated, the details of that request should not be modified. 
 To update attributes (like an organization’s name) after a domain’s approval, 
-go to <a class="usa-button usa-button--unstyled text-underline" href="{% url 'admin:registrar_domain_changelist' %}">Domains</a>. 
+go to <a class="text-underline" href="{% url 'admin:registrar_domain_changelist' %}">Domains</a>. 
 Similar fields display on each Domain page, but edits made there will not affect the corresponding domain request.
 </p>

src/registrar/templates/django/admin/includes/descriptions/draft_domain_description.html

@@ -6,5 +6,5 @@ the original name they listed and the new name will appear as separate records.
 
 <p>
 This table does not include “alternative domains,” 
-which are housed in the <a class="usa-button usa-button--unstyled text-underline" href="{% url 'admin:registrar_website_changelist' %}">Websites</a> table.
+which are housed in the <a class="text-underline" href="{% url 'admin:registrar_website_changelist' %}">Websites</a> table.
 </p>

src/registrar/templates/django/admin/includes/descriptions/host_description.html

@@ -6,6 +6,6 @@ Entries in the Hosts table indicate the relationship between an approved domain
 <p>
 In general, you should not modify these values here. They should be updated directly inside the registrar. 
 To update a domain’s name servers and/or IP addresses, 
-in the registrar, go to the domain in <a class="usa-button usa-button--unstyled text-underline" href="{% url 'admin:registrar_domain_changelist' %}">Domains</a>, 
+in the registrar, go to the domain in <a class="text-underline" href="{% url 'admin:registrar_domain_changelist' %}">Domains</a>, 
 then click the "Manage domain" button.
 </p>

src/registrar/templates/django/admin/includes/descriptions/logentry_description.html

@@ -3,5 +3,5 @@ Log entries represent instances where something was created, updated, or deleted
 The table on this page is useful for searching actions across all records. 
 To understand what happened to an individual record (like a domain request), 
 it’s better to go to that specific page 
-(<a class="usa-button usa-button--unstyled text-underline" href="{% url 'admin:registrar_domainrequest_changelist' %}">Domain requests</a>) and click on the “History” button.  
+(<a class="text-underline" href="{% url 'admin:registrar_domainrequest_changelist' %}">Domain requests</a>) and click on the “History” button.  
 </p>

src/registrar/templates/django/admin/includes/descriptions/user_description.html

@@ -11,6 +11,6 @@ and their existing requests are locked. They will see a 403 error if  they try t
 
 <p>
 Each user record displays the associated “contact” info for that user, 
-which is the same info found in the <a class="usa-button usa-button--unstyled text-underline" href="{% url 'admin:registrar_contact_changelist' %}">Contacts</a> table. 
+which is the same info found in the <a class="text-underline" href="{% url 'admin:registrar_contact_changelist' %}">Contacts</a> table. 
 Updating these details on the user record will also update the corresponding contact record for that user. 
 </p>

src/registrar/templates/django/admin/includes/descriptions/user_group_description.html

@@ -1,6 +1,6 @@
 <p>
 Groups are a way to bundle admin permissions so they can be easily assigned to multiple users. 
-Once a group is created, it can be assigned to people via the <a class="usa-button usa-button--unstyled text-underline" href="{% url 'admin:registrar_user_changelist' %}">Users</a> table. 
+Once a group is created, it can be assigned to people via the <a class="text-underline" href="{% url 'admin:registrar_user_changelist' %}">Users</a> table. 
 </p>
 
 <p>

src/registrar/templates/django/admin/includes/descriptions/website_description.html

@@ -3,6 +3,6 @@ This table lists all the “current websites” and “alternative domains” th
 </p>
 
 <p>
-This does not include any “requested domains” that have appeared within the <a class="usa-button usa-button--unstyled text-underline" href="{% url 'admin:registrar_domainrequest_changelist' %}">Domain requests</a> table. 
-Those names are managed in the <a class="usa-button usa-button--unstyled text-underline" href="{% url 'admin:registrar_draftdomain_changelist' %}">Draft domains<a/> table.
+This does not include any “requested domains” that have appeared within the <a class="text-underline" href="{% url 'admin:registrar_domainrequest_changelist' %}">Domain requests</a> table. 
+Those names are managed in the <a class="text-underline" href="{% url 'admin:registrar_draftdomain_changelist' %}">Draft domains<a/> table.
 </p>