CI: Automatic .md and .mdx formatting

Author: github-actions[bot]

docs/develop/ruby/set-up-local-ruby.mdx

@@ -12,8 +12,8 @@ tags:
   - Temporal SDKs
 ---
 
-This guide walks you through setting up the Temporal Ruby SDK and running your first Workflow. 
-In just a few steps, you'll install the SDK and start a local development server. 
+This guide walks you through setting up the Temporal Ruby SDK and running your first Workflow.
+In just a few steps, you'll install the SDK and start a local development server.
 To validate that your local environment is correctly installed, we will execute a Workflow that will output "Hello, Temporal".
 
 ## 1. Installation
@@ -115,8 +115,9 @@ You'll be able to monitor your Workflows through the Web UI as they execute.
 > ```
 
 ## 3. Write Your First Activity and Workflow
-Now that you have the server running, it's time to create your first Temporal application. 
-In Temporal, you'll create two files an Activity file labeled `say_hello_activity.rb` and a Workflow file labeled `say_hello_workflow.rb`. 
+
+Now that you have the server running, it's time to create your first Temporal application.
+In Temporal, you'll create two files an Activity file labeled `say_hello_activity.rb` and a Workflow file labeled `say_hello_workflow.rb`.
 
 <Tabs>
   <TabItem value="activity" label="Activity (say_hello_activity.rb)">
@@ -156,15 +157,15 @@ require_relative 'say_hello_activity'
 </Tabs>
 
 A Temporal Workflow is your business logic, defined in code, outlining each step in your process.
-Activities are the individual units of work in your Workflow. 
-Activities often involve interacting with the outside world, such as sending emails, making network requests, writing to a database, or calling an API, which are prone to failure. 
-You can call Activities directly from your Workflow code. 
-If an Activity fails, Temporal automatically retries it based on your configuration. 
-
+Activities are the individual units of work in your Workflow.
+Activities often involve interacting with the outside world, such as sending emails, making network requests, writing to a database, or calling an API, which are prone to failure.
+You can call Activities directly from your Workflow code.
+If an Activity fails, Temporal automatically retries it based on your configuration.
 
 ## 4. Run a Worker
-With your Activity and Workflow defined, you need a Worker to execute them. 
-Create a file labeled `worker.rb`.  
+
+With your Activity and Workflow defined, you need a Worker to execute them.
+Create a file labeled `worker.rb`.\
 Workers, which are part of your application and provided by the Temporal SDK, then carry out the tasks defined in your Workflow.
 
 <Tabs>
@@ -191,21 +192,22 @@ worker.run(shutdown_signals: ['SIGINT'])
 </TabItem>
 </Tabs>
 
-Workers are a crucial part of your Temporal application as they're what actually execute the tasks defined in your Workflows and Activities. 
+Workers are a crucial part of your Temporal application as they're what actually execute the tasks defined in your Workflows and Activities.
 For more information on Workers, see [Understanding Temporal](/evaluate/understanding-temporal#workers) and a [deep dive into Workers](/workers).
 
-::: note 
+::: note
 Start your Worker by running:
-`ruby worker.rb` 
+`ruby worker.rb`
 
-Keep this running in another terminal window. 
+Keep this running in another terminal window.
 You should see output indicating that the Worker has started and is polling for tasks.
 
-::: 
+:::
 
 ## 5. Execute a Workflow and See the Result
-With your Worker running and listening for tasks, you can now trigger a Workflow execution. 
-This final step will validate that everything is working correctly with your file labeled `execute_workflow.rb`. 
+
+With your Worker running and listening for tasks, you can now trigger a Workflow execution.
+This final step will validate that everything is working correctly with your file labeled `execute_workflow.rb`.
 
 Run this script in a new terminal window with the following command: `ruby execute_workflow.rb`
 
@@ -237,16 +239,16 @@ puts "Result: #{result}"
 Result: Hello, Temporal!
 ```
 
-You've successfully executed your first Temporal Workflow. 
+You've successfully executed your first Temporal Workflow.
 If you check the Temporal Web UI at http://localhost:8233, you'll gain visibility into your Workflow Execution with details listed about its progress and completion.
 
-## Next Steps 
+## Next Steps
 
 Now that your local environment is set up, you can explore the full capabilities of Temporal by following the [Getting Started with Ruby tutorials](https://learn.temporal.io/getting_started/ruby/).
 These tutorials will walk you through building and running your first Workflows using the Ruby SDK.
 
 If you would like to better understand the underlying concepts behind what you have built, visit [Understanding Temporal](/understanding-temporal), which provides a basic high level overview of how the Temporal works.
-For more learning by doing, you can also explore our collection of [Ruby code samples](https://github.com/temporalio/samples-ruby) on GitHub. 
+For more learning by doing, you can also explore our collection of [Ruby code samples](https://github.com/temporalio/samples-ruby) on GitHub.
 
-To take the next step toward building production-ready applications, check out the [Core Application section](/develop/ruby/core-application) of the Ruby Developer Guide. 
-This will help you understand how Temporal applications are structured.
+To take the next step toward building production-ready applications, check out the [Core Application section](/develop/ruby/core-application) of the Ruby Developer Guide.
+This will help you understand how Temporal applications are structured.