Updates

Author: viren-nadkarni

Diff for: content/en/user-guide/aws/fis/index.md

@@ -28,7 +28,7 @@ FIS defines the following elements:
 1. Duration of the disruption.
 
 Together this is termed as an Experiment.
-After the designated time, FIS restores systems to their original state and/or ceases introducing faults.
+After the designated time, running experiments restore systems to their original state and cease introducing faults.
 
 {{< callout "note" >}}
 FIS experiment emulation is part of LocalStack Enterprise.
@@ -37,10 +37,9 @@ If you'd like to try it out, please [contact us](https://www.localstack.cloud/de
 
 FIS actions can be categorized into two main types:
 
-1. Single-time events — For example, the `aws:ec2:stop-instances` FIS action, which sends a [`StopInstances`](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_StopInstances.html) API to specific EC2 instances.
+1. One-time events: For example, the `aws:ec2:stop-instances` FIS action, which sends a [`StopInstances`](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_StopInstances.html) API to specific EC2 instances.
 Some of these events can automatically be undone after a defined time, such as sending a [`StartInstances`](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_StartInstances.html) command to the affected instances.
-1. Inducing API errors in response to a specified percentage of API calls.
-For instance, using `aws:fis:inject-api-unavailable-error` to introduce an HTTP 503 error.
+1. Probabilistic API errors: For instance, using `aws:fis:inject-api-unavailable-error` to introduce an HTTP 503 error.
 
 ## Getting started
 
@@ -233,9 +232,7 @@ LocalStack FIS currently supports the following actions:
 - **`aws:rds:reboot-db-instances`**: Runs EC2 RebootInstances on the target EC2 instances.
 - **`aws:ssm:send-command`**: Runs the Systems Manager SendCommand on the target EC2 instances.
 
-{{< callout "note" >}}
 If you would like support for more FIS actions, please make a feature request on [GitHub](https://github.com/localstack/localstack/issues/new/choose).
-{{< /callout >}}
 
 ## Current Limitations
 

Diff for: content/en/user-guide/aws/kinesis/index.md

@@ -207,4 +207,4 @@ The following code snippets and sample applications provide practical examples o
 ## Limitations
 
 In multi-account setups, each AWS account launches a separate instance of Kinesis Mock, which is very resource intensive when a large number of AWS accounts are used.
-An [open Kinesis Mock issue](https://github.com/etspaceman/kinesis-mock/issues/377) is being used to keep track of this feature.
+[This Kinesis Mock issue](https://github.com/etspaceman/kinesis-mock/issues/377) is being used to keep track of this feature.

Diff for: content/en/user-guide/aws/mwaa/index.md

@@ -8,15 +8,15 @@ tags: ["Pro image"]
 
 ## Introduction
 
-Managed Workflows for Apache Airflow (MWAA) is a fully managed service by AWS that simplifies the deployment, management, and scaling of Apache Airflow workflows in the cloud.
+Managed Workflows for Apache Airflow (MWAA) is a fully managed service by AWS that simplifies the deployment, management, and scaling of [Apache Airflow](https://airflow.apache.org/) workflows in the cloud.
 MWAA leverages the familiar Airflow features and integrations while integrating with S3, Glue, Redshift, Lambda, and other AWS services to build data pipelines and orchestrate data processing workflows in the cloud.
 
 LocalStack allows you to use the MWAA APIs in your local environment to allow the setup and operation of data pipelines.
-The supported APIs are available on our [API coverage page](https://docs.localstack.cloud/references/coverage/coverage_mwaa/), which provides information on the extent of MWAA's integration with LocalStack.
+The supported APIs are available on the [API coverage page](https://docs.localstack.cloud/references/coverage/coverage_mwaa/).
 
 ## Getting started
 
-This guide is designed for users new to Managed Workflows for Apache Airflow and assumes basic knowledge of the AWS CLI and our [`awslocal`](https://github.com/localstack/awscli-local) wrapper script.
+This guide is designed for users new to MWAA and assumes basic knowledge of the AWS CLI and our [`awslocal`](https://github.com/localstack/awscli-local) wrapper script.
 
 Start your LocalStack container using your preferred method.
 We will demonstrate how to create an Airflow environment and access the Airflow UI.
@@ -153,3 +153,7 @@ The Resource Browser allows you to perform the following actions:
 - **View Environment**: View details of an existing MWAA environment by clicking on the environment name.
 - **Edit Environment**: Edit an existing MWAA environment by clicking on the **Edit** button after clicking on the environment name.
 - **Delete Environment**: Select the environment name and click on the **Actions** button followed by **Remove Selected** button.
+
+## Limitations
+
+- LocalStack MWAA does not support [startup scripts](https://docs.aws.amazon.com/mwaa/latest/userguide/using-startup-script.html)

Diff for: content/en/user-guide/aws/ram/index.md

@@ -8,7 +8,7 @@ Resource Access Manager (RAM) helps resources to be shared across AWS accounts,
 
 On AWS, RAM is an abstraction on top of AWS Identity and Access Management (IAM) which can manage resource-based policies to supported resource types.
 
-LocalStack supports RAM in the Pro edition.
+RAM is available in LocalStack Pro.
 The supported API operations can be found on the [API coverage page](https://docs.localstack.cloud/references/coverage/coverage_ram/).
 
 ## Getting started
@@ -34,7 +34,7 @@ $ awslocal ram create-resource-share \
     --resource-arn arn:aws:appsync:eu-central-1:000000000000:apis/wcgmjril5wuyvhmpildatuaat3
 {{< /command >}}
 
-## Current Limitations
+## Limitations
 
 LocalStack RAM supports emulated sharing for EC2 Subnets only.
 Only specified account principals are granted access to the shared subnets, and associated VPC and route tables.

Diff for: content/en/user-guide/aws/ses/index.md

@@ -12,8 +12,8 @@ persistence: supported
 Simple Email Service (SES) is an emailing service that can be integrated with other cloud-based services.
 It provides API to facilitate email templating, sending bulk emails and more.
 
-LocalStack supports SES v1 in the Community image, while SES v2 and SMTP integration is supported in the Pro image.
-The supported APIs are available on the API coverage page for [SES v1](https://docs.localstack.cloud/references/coverage/coverage_ses/) and [SES v2](https://docs.localstack.cloud/references/coverage/coverage_sesv2/).
+SESv1 is available in LocalStack Community image, while SESv2 and SMTP integration is available in LocalStack Pro.
+The supported APIs are available on the API coverage page for [SESv1](https://docs.localstack.cloud/references/coverage/coverage_ses/) and [SESv2](https://docs.localstack.cloud/references/coverage/coverage_sesv2/).
 
 ## Getting Started
 
@@ -40,7 +40,7 @@ $ awslocal ses list-identities
 
 {{< callout >}}
 On AWS, verifying email identities or domain identities require additional steps like changing DNS configuration or clicking verification links respectively.
-In LocalStack, verifying identities require no additional steps.
+In LocalStack, identities are automatically verified.
 {{< /callout >}}
 
 Next, emails can be sent using the `SendEmail` operation.
@@ -56,12 +56,11 @@ $ awslocal ses send-email \
 {{< /command >}}
 
 {{< callout >}}
-In the Community image, no emails are actually sent.
-Hence this operation is mocked.
-In the Pro image however, emails are sent via an SMTP server.
+In LocalStack Community, all operations are mocked and no real emails are sent.
+In LocalStack Pro, it is possible to send real emails via an SMTP server.
 {{< /callout >}}
 
-## Sent Emails
+## Retrieve Sent Emails
 
 LocalStack keeps track of all sent emails for retrospection.
 Sent messages can be retrieved in following ways:
@@ -101,11 +100,12 @@ $ curl --silent localhost.localstack.cloud:4566/_aws/[email protected]
 
 ## SMTP Integration
 
-The Pro image supports sending emails via an SMTP server.
-Refer to the [Configuration]({{< ref "configuration#emails" >}}) guide for instructions on how to configure the connection parameters of your SMTP server (`SMTP_HOST`/`SMTP_USER`/`SMTP_PASS`).
+LocalStack Pro supports sending emails via an SMTP server.
+To enable this, set the connections parameters and access credentials for the server in the configuration.
+Refer to the [Configuration]({{< ref "configuration#emails" >}}) guide for details.
 
 {{< callout "tip" >}}
-If you do not have access to a proper SMTP server, you can use tools like [MailDev](https://github.com/maildev/maildev) or [smtp4dev](https://github.com/rnwood/smtp4dev).
+If you do not have access to a live SMTP server, you can use tools like [MailDev](https://github.com/maildev/maildev) or [smtp4dev](https://github.com/rnwood/smtp4dev).
 These run as Docker containers on your local machine.
 Make sure they run in the same Docker network as the LocalStack container.
 {{< /callout >}}
@@ -124,7 +124,7 @@ The Resource Browser allows you to perform following actions:
   You can the view the details of a sent email by selecting them from the list.
 - **Send Emails**: On selecting an email identity, click **Send Message** and specify destination fields (To, CC and BCC addresses) and the body (Plaintext, HTML) to send an email.
 
-## Current Limitations
+## Limitations
 
-It is currently not possible to [receive emails via SES](https://docs.aws.amazon.com/ses/latest/dg/receiving-email.html) in LocalStack.
-Consequently, all operations related to Receipt Rules are currently mocked.
+- It is currently not possible to [receive emails via SES](https://docs.aws.amazon.com/ses/latest/dg/receiving-email.html) in LocalStack.
+- All operations related to Receipt Rules are mocked.

Diff for: content/en/user-guide/aws/transcribe/index.md

@@ -8,20 +8,16 @@ persistence: supported
 
 ## Introduction
 
-Transcribe is a service provided by Amazon Web Services (AWS) that offers automatic speech recognition (ASR) capabilities.
+Transcribe is a service provided by AWS that offers automatic speech recognition (ASR) capabilities.
 It enables developers to convert spoken language into written text, making it valuable for a wide range of applications, from transcription services to voice analytics.
 
 LocalStack allows you to use the Transcribe APIs for offline speech-to-text jobs in your local environment.
 The supported APIs are available on our [API Coverage Page](https://docs.localstack.cloud/references/coverage/coverage_transcribe/), which provides information on the extent of Transcribe integration with LocalStack.
 
-{{< callout >}}
-LocalStack's Transcribe relies on the offline speech-to-text service called [Vosk](https://alphacephei.com/vosk/).
-Therefore, LocalStack requires an internet connection during the initial creation of a transcription job for a specific language.
-This initial connection is required to download and cache the language model.
-
-Once the language model is cached, subsequent transcriptions for the same language can be performed offline.
-These language models typically have a size of around 50 MiB, and they are saved to the cache directory (for more details, refer to the [Filesystem Layout]({{< ref "filesystem" >}}) section).
-{{< /callout >}}
+LocalStack Transcribe uses an offline speech-to-text library called [Vosk](https://alphacephei.com/vosk/).
+It requires an active internet connection to download the language model.
+Once the language model is downloaed, subsequent transcriptions for the same language can be performed offline.
+Language models typically have a size of around 50 MiB and are saved in the cache directory (see [Filesystem Layout]({{< ref "filesystem" >}})).
 
 ## Getting Started
 
@@ -123,16 +119,16 @@ The following languages and dialects are supported:
 
 | Language         | Language Code |
 | ---------------- | ------------- |
-| Catalan          | `ca_ES`       |
-| Czech            | `cs_CZ`       |
+| Catalan          | `ca-ES`       |
+| Czech            | `cs-CZ`       |
 | German           | `de-DE`       |
 | English, British | `en-GB`       |
 | English, Indian  | `en-IN`       |
 | English, US      | `en-US`       |
 | Spanish          | `es-ES`       |
 | Farsi            | `fa-IR`       |
 | French           | `fr-FR`       |
-| Gujarati         | `gu_IN`       |
+| Gujarati         | `gu-IN`       |
 | Hindi            | `hi-IN`       |
 | Italian          | `it-IT`       |
 | Japan            | `ja-JP`       |