edits temporal service

docs/evaluate/how-it-works.mdx

@@ -15,14 +15,12 @@ tags:
   - how-temporal-works
 ---
 
-# How Temporal Works
-
 Temporal provides a comprehensive platform for building distributed applications with a focus on durability and reliability. 
 
 ## Resilient applications by default
 
-Temporal ensures your applications are reliable by default, handling everything from minor network outages to significant issues like unexpected reboots, application crashes, or hardware failures.
-By offloading the responsibility of failure management from the application to the platform, developers are freed from extensive coding, testing, and maintenance tasks. 
+Temporal ensures your applications are reliable by default, handling everything from minor network outages to significant issues like unexpected reboots, or hardware failures.
+By offloading the responsibility of failure management from the application to the platform, this removes the need for extensive coding, testing, and maintenance tasks. 
 
 This shift simplifies the development process and enables your application to seamlessly recover from disruptions. 
 It does so by automatically reconstructing its previous state. 
@@ -41,16 +39,16 @@ The Worker runs the Workflow and Activity code.
 
 ### Activity
 Activities are functions which encapsulate logic that can potentially fail, such as network calls, file operations,  or random number generation. 
-Activities are invoked in Workflow code and the Server coordinates with the application to execute them.
+Activities are invoked in Workflow code and the Temporal Service coordinates with the application to execute them.
 
 ![HIW Recent Workflows page](/img/how-it-works/hiw-activityinvocation-continuingworkflow-merge.png)
 
-### Server
-Temporal consists of two components, the Server and an SDK in your preferred language such as Go, .NET, Java, Python, PHP, or Typescript. 
-The Server logs the progress and state of your application. 
-Once the application finishes executing the Activity, it communicates with the Server, which records the Activity's completion in the Workflow's Event History. 
-The Activity invocation is handled by the Server. 
-The Server updates the Event History and creates a Task for executing the Activity.
+### Temporal Service
+Temporal consists of two components, the [Temporal Service](/evaluate/major-components#temporal-service) and an SDK in your preferred language such as Go, .NET, Java, Python, PHP, or Typescript. 
+The Temporal Service logs the progress and state of your application. 
+Once the application finishes executing the Activity, it communicates with the Temporal Service, which records the Activity's completion in the Workflow's Event History. 
+The Activity invocation is handled by the Temporal Service. 
+The Temporal Service updates the Event History and creates a Task for executing the Activity.
 
 ![HIW Recent Workflows page](/img/how-it-works/hiw-yourapplicationdepending-activityexecution-merge.png)
 
@@ -63,39 +61,10 @@ Temporal provides built-in solutions for timers, event sourcing, state checkpoin
 ![HIW Recent Workflows page](/img/how-it-works/hiw-recoveringfromfailure-mergeofthree.png)
 
 ### Concluding the Workflow
-In this example, there are two Activities. The second Activity is complete, but the Workflow function sill has additional code to run. 
-The Temporal Server creates a new Task requesting that the application run the additional code.
+In this example, there are two Activities. The second Activity is complete, but the Workflow function still has additional code to run. 
+The Temporal Temporal Service creates a new Task requesting that the application run the additional code.
 
 ![HIW Recent Workflows page](/img/how-it-works/hiw-concludingtheworkflow-temporalserver-merge.png)
 
-:::info
-**Follow one of our tutorials to [Get started](https://learn.temporal.io/getting_started/) learning how to develop Workflows and Activities and run them in Worker Processes.**
-
-Or jump straight to a Temporal SDK feature guide:
-
-- [Go SDK Core application feature guide](/develop/go/temporal-client)
-- [Java SDK Core application feature guide](/develop/java/temporal-client#connect-to-development-service)
-- [PHP SDK Core application feature guide](/dev-guide/php/foundations#connect-to-a-dev-cluster)
-- [Python SDK Core application feature guide](/dev-guide/python/foundations#connect-to-a-dev-cluster)
-- [TypeScript SDK Core application feature guide](/dev-guide/typescript/foundations#connect-to-a-dev-cluster)
-
-For a deep dive into Temporal Workflows, Activities, and Workers, visit the following Temporal Encyclopedia pages or enroll in one of [our courses](https://learn.temporal.io/courses/):
-
-- [Temporal Workflows](/workflows)
-- [Temporal Activities](/activities)
-- [Temporal Workers](/workers)
-:::
-
-
-
-
-
-
-{/* The Workflow code uses Temporal SDK APIs to orchestrate the steps of the application. 
-A Workflow executes Activities (other functions that interact with external systems), handles and sends messages (Queries, Signals, Updates), and interacts with other Workflows. 
-This Workflow code, while executing, can be paused, resumed, and even migrated across physical machines without losing state.
-
-Use your own tools and existing infrastructure.
 
-insert scrollycode/codehike */}
 

docs/evaluate/major-components.mdx

@@ -40,7 +40,7 @@ Or jump straight into the SDK docs for your preferred language:
 
 For a deep dive into how Temporal SDKs work, visit the [Temporal SDKs Encyclopedia page](/encyclopedia/temporal-sdks).
 
-## Temporal Service
+## Temporal Service {#temporal-service}
 
 **What is a Temporal Service?**