Merge pull request #56 from IABTechLab/eee-uid2-4846-server-side-gss-copyedits

eiman-eltigani-ttd · web-flow · commit e1a89c21c27d · 2025-11-04T12:16:34.000-07:00
Minor copy edits to server side GSS integration example
diff --git a/web-integrations/google-secure-signals/server-side/views/header.html b/web-integrations/google-secure-signals/server-side/views/header.html
@@ -29,16 +29,16 @@
   <body>
     <h1>Server-Side <%- identityName %> Integration Example with Google Secure Signals</h1>
     <p class="intro">
-      This example demonstrates how a content publisher can use the <%- identityName %> services to implement the
-      <a href="<%- docsBaseUrl %>/guides/integration-google-ss#server-side-integration">server-side <%- identityName %> integration workflow with Secure Signals</a>. [<a
+      This example demonstrates how a content publisher can use the <%- identityName %> services with Secure Signals to implement
+      <a href="<%- docsBaseUrl %>/guides/integration-google-ss#server-side-integration">Server-Side Integration</a>. [<a
         href="https://github.com/IABTechLab/uid2-examples/tree/main/web-integrations/google-secure-signals/server-side"
         >Source Code</a
       >]
       <br />
       <br />
-      This assumes that the publisher has implemented
-      <a href="<%- docsBaseUrl %>/guides/integration-publisher-server-side"><%- identityName %> Server-Side integration</a>
-      on the backend and is able to pass the resulting <%- identityName %> identity response to the front end.
+      This assumes that the publisher has implemented <%- identityName %> 
+      <a href="<%- docsBaseUrl %>/guides/integration-publisher-server-side">Server-Side Integration</a>
+      on the back end and can pass the resulting <%- identityName %> identity response to the front end.
     </p>
   </body>
 </html>
