update encore comparison (#673)

Co-authored-by: Jye Cusch <[email protected]>

Author: davemooreuws

docs/misc/comparison/encore.mdx

@@ -9,9 +9,9 @@ Nitric is a framework that empowers developers to build complete cloud applicati
 These are the main differences between the two:
 
 1. **Cloud Provider Support:** Nitric is provider-agnostic, capable of deploying to multiple cloud providers such as AWS, Google Cloud, and Azure. Encore currently deploys to AWS or Google Cloud.
-2. **Language Support:** Nitric provides libraries for TypeScript/JavaScript, Python, Go, C# .NET and Java, allowing developers to choose their preferred language. Currently Encore supports Go, with TypeScript scheduled for Preview.
-3. **Infrastructure Provisioning:** Nitric uses Pulumi by default for provisioning cloud resources, but also allows the use of [custom providers](/providers/custom/create). Encore uses a hosted provisioning engine via their online platform.
-4. **Open Source:** As an open-source framework, Nitric does not require a platform or subscription to deploy applications, while Encore requires sign-up and may involve additional costs.
+2. **Language Support:** Nitric provides libraries for TypeScript/JavaScript, Python, Go, and Dart. Additional languages can be supported using Nitric's gRPC API, allowing developers to choose their preferred language. Currently Encore supports Go and TypeScript.
+3. **Infrastructure Provisioning:** Nitric uses Pulumi or Terraform by default for provisioning cloud resources, but also allows the use of [custom providers](/providers/custom/create). Encore uses a hosted provisioning engine via their online platform.
+4. **Open Source:** As an open-source framework, Nitric does not require a platform or subscription to deploy applications. Encore's language frameworks are provided as open-source software, however infrastructure provisioning requires users to create their own IaC scripts or sign-up to Encore's hosted platform, which may incur additional costs.
 
 ## Code Comparison
 
@@ -72,13 +72,13 @@ type Response struct {
 
 </Row>
 
-The Nitric example shows an API where HTTP request handling is achieved using `faas.HttpContext`, providing control over the request and response objects. The Encore example demonstrates an API where HTTP request handling is reflected through the function parameters and return types, with defined structs for responses.
+The Nitric example shows an API where HTTP request handling is achieved using `apis.Ctx`, providing control over the request and response objects. The Encore example demonstrates an API where HTTP request handling is reflected through the function parameters and return types, with defined structs for responses.
 
 ## Differences
 
 |                      | Nitric                                                           | Encore                     |
 | -------------------- | ---------------------------------------------------------------- | -------------------------- |
-| Language             | Your choice                                                      | Go                         |
+| Language             | Your choice                                                      | Go, TypeScript             |
 | Lines of code        | 26                                                               | 15                         |
 | Cloud Infrastructure | Inferred                                                         | Inferred                   |
 | Extensibility        | [Custom providers](/providers/custom/create) can be created      | No                         |