Fix typos in Java SDK documentation

docs/develop/java/core-application.mdx

@@ -129,7 +129,7 @@ r2.retryNow();
 The same technique can be used to query Workflows using a base Workflow interface.
 
 Note that this approach does not apply to `@WorkflowMethod` annotations, meaning that when using a base interface, it should not include any `@WorkflowMethod` methods.
-To illustrate this, lets' say that we define the following **invalid** code:
+To illustrate this, let's say that we define the following **invalid** code:
 
 ```java
 // INVALID CODE!
@@ -207,7 +207,7 @@ Related references:
 
 **How to customize your Workflow Type using the Java SDK.**
 
-Workflows have a Type that are referred to as the Workflow name.
+Workflows have a Type that is referred to as the Workflow name.
 
 The following examples demonstrate how to set a custom name for your Workflow Type.
 
@@ -339,7 +339,7 @@ An Activity interface can have any number of parameters.
 All inputs should be serializable by the default Jackson JSON Payload Converter.
 
 When implementing Activities, be mindful of the amount of data that you transfer using the Activity invocation parameters or return values as these are recorded in the Workflow Execution Events History.
-Large Events Histories can adversely impact performance.
+Large Event Histories can adversely impact performance.
 
 You can create a custom object, and pass it to the Activity interface, as shown in the following example.
 
@@ -478,7 +478,7 @@ Systems such as Prometheus may ignore metrics with tags using unsupported charac
 
 Calls to spawn [Activity Executions](/activity-execution) are written within a [Workflow Definition](/workflow-definition).
 The call to spawn an Activity Execution generates the [ScheduleActivityTask](/references/commands#scheduleactivitytask) Command.
-This results in the set of three [Activity Task](/tasks#activity-task) related Events ([ActivityTaskScheduled](/references/events#activitytaskscheduled), [ActivityTaskStarted](/references/events#activitytaskstarted), and ActivityTask[Closed])in your Workflow Execution Event History.
+This results in the set of three [Activity Task](/tasks#activity-task) related Events ([ActivityTaskScheduled](/references/events#activitytaskscheduled), [ActivityTaskStarted](/references/events#activitytaskstarted), and ActivityTask[Closed]) in your Workflow Execution Event History.
 
 A single instance of the Activities implementation is shared across multiple simultaneous Activity invocations.
 Activity implementation code should be _idempotent_.

docs/develop/java/message-passing.mdx

@@ -736,7 +736,7 @@ When working with Updates, you may encounter these errors:
   A [Workflow Task Failure](/references/failures) causes the server to retry Workflow Tasks indefinitely. What happens to your Update request depends on its stage:
   - If the request hasn't been accepted by the server, you receive a `FAILED_PRECONDITION` [`WorkflowServiceException`](https://javadoc.io/doc/io.temporal/temporal-sdk/latest/io/temporal/client/WorkflowServiceException.html) exception.
   - If the request has been accepted, it is durable.
-    Once the Workflow is healthy again after a code deploy, use an `WorkflowUpdateHandle`](https://javadoc.io/doc/io.temporal/temporal-sdk/latest/io/temporal/client/WorkflowUpdateHandle.html) to fetch the Update result.
+    Once the Workflow is healthy again after a code deploy, use a [`WorkflowUpdateHandle`](https://javadoc.io/doc/io.temporal/temporal-sdk/latest/io/temporal/client/WorkflowUpdateHandle.html) to fetch the Update result.
 
 - **The Workflow finished while the Update handler execution was in progress**:
   You'll receive a [`WorkflowServiceException`](https://javadoc.io/doc/io.temporal/temporal-sdk/latest/io/temporal/client/WorkflowServiceException.html) "workflow execution already completed"`.

docs/develop/java/observability.mdx

@@ -47,7 +47,7 @@ For a complete list of metrics capable of being emitted, see the [SDK metrics re
 - For a list of metrics, see the [SDK metrics reference](/references/sdk-metrics).
 - For an end-to-end example that exposes metrics with the Java SDK, refer to the [samples-java](https://github.com/temporalio/samples-java/tree/main/core/src/main/java/io/temporal/samples/metrics) repo.
 
-To emit metrics with the Java SDK, use the[`MicrometerClientStatsReporter`](https://github.com/temporalio/sdk-java/blob/55ee7894aec427d7e384c3519732bdd61119961a/src/main/java/io/temporal/common/reporter/MicrometerClientStatsReporter.java#L34) class to integrate with Micrometer MeterRegistry configured for your metrics backend.
+To emit metrics with the Java SDK, use the [`MicrometerClientStatsReporter`](https://github.com/temporalio/sdk-java/blob/55ee7894aec427d7e384c3519732bdd61119961a/src/main/java/io/temporal/common/reporter/MicrometerClientStatsReporter.java#L34) class to integrate with Micrometer MeterRegistry configured for your metrics backend.
 [Micrometer](https://micrometer.io/docs) is a popular Java framework that provides integration with Prometheus and other backends.
 
 The following example shows how to use `MicrometerClientStatsReporter` to define the metrics scope and set it with the `WorkflowServiceStubsOptions`.
@@ -229,7 +229,7 @@ Each `SearchAttribute` object represents a custom attribute name, and the value
 - Text
 
 In this example `isOrderFailed` is set as a Search Attribute. This attribute is
-useful for querying Workflows based the success/failure of customer orders.
+useful for querying Workflows based on the success/failure of customer orders.
 
 ### How to upsert Search Attributes {#upsert-search-attributes}
 

docs/develop/java/schedules.mdx

@@ -30,9 +30,9 @@ This page shows how to do the following:
 
 ## How to Schedule a Workflow {#schedule-a-workflow}
 
-Scheduling Workflows is a crucial aspect of any automation process, especially when dealing with time-sensitive tasks. By scheduling a Workflow, you can automate repetitive tasks, reduce the need for manual intervention, and ensure timely execution of your business processes
+Scheduling Workflows is a crucial aspect of any automation process, especially when dealing with time-sensitive tasks. By scheduling a Workflow, you can automate repetitive tasks, reduce the need for manual intervention, and ensure timely execution of your business processes.
 
-Use any of the following action to help Schedule a Workflow Execution and take control over your automation process.
+Use any of the following actions to help Schedule a Workflow Execution and take control over your automation process.
 
 ### How to create a Schedule in Java {#create-schedule}
 

docs/develop/java/spring-boot-integration.mdx

@@ -206,7 +206,7 @@ Where `OptionsType` may be one of:
 
 ## Testing {#testing}
 
-The Temporal Spring Boot integration also has easy support for testing your Temporal code. Add the following to your `application.yml` to reconfigure the client work through `io.temporal.testing.TestWorkflowEnvironment` that uses in-memory Java Test Server:
+The Temporal Spring Boot integration also has easy support for testing your Temporal code. Add the following to your `application.yml` to reconfigure the client to work through `io.temporal.testing.TestWorkflowEnvironment` that uses in-memory Java Test Server:
 
 ```
 spring.temporal:

docs/develop/java/temporal-client.mdx

@@ -548,7 +548,7 @@ To connect to Temporal Cloud using mTLS, you need to provide the mTLS CA certifi
 use the `SimpleSslContextBuilder` to build an SSL context. Then use the
 `WorkflowServiceStubsOptions.Builder.setSslContext` method to set the SSL context.
 
-When you use a remote service, you don't use the `newLocalServicesStubs` convenience method. Instead, set your
+When you use a remote service, you don't use the `newLocalServiceStubs` convenience method. Instead, set your
 connection details as stub configuration options:
 
 <!--SNIPSTART javasdk-build-caller-app-using-temporal-cloud {"selectedLines": ["46-54"]}-->

docs/develop/java/temporal-nexus.mdx

@@ -575,7 +575,7 @@ When a Nexus operation is started the caller can specify different cancellation
 
 - `ABANDON` - Do not request cancellation of the operation.
 - `TRY_CANCEL` - Initiate a cancellation request and immediately report cancellation to the caller. Note that this type doesn't guarantee that cancellation is delivered to the operation handler if the caller exits before the delivery is done.
-- `WAIT_REQUESTED` ` Request cancellation of the operation and wait for confirmation that the request was received. Doesn't wait for actual cancellation.
+- `WAIT_REQUESTED` - Request cancellation of the operation and wait for confirmation that the request was received. Doesn't wait for actual cancellation.
 - `WAIT_COMPLETED` - Wait for operation completion. Operation may or may not complete as cancelled.
 
 The default is `WAIT_COMPLETED`. Users can set a different option on the `NexusServiceOptions` by calling `.setCancellationType()` on `NexusServiceOptions.Builder`.

docs/develop/java/versioning.mdx

@@ -7,7 +7,7 @@ toc_max_heading_level: 2
 description: The Temporal Platform ensures deterministic Workflow code, offering versioning features in the Java SDK with Workflow Patching APIs and Worker Build Ids for efficient updates.
 keywords:
   - determinism
-  - go sdk
+  - java sdk
   - patching
   - versioning
   - workflows