fix: remove echo from quickstart

docs/docs/getting-started/quick-start.md

@@ -88,7 +88,7 @@ import (
 )
 
 //ftl:verb
-func Echo(ctx context.Context, name ftl.Option[string]) (string, error) {
+func Hello(ctx context.Context, name ftl.Option[string]) (string, error) {
     return fmt.Sprintf("Hello, %s!", name.Default("anonymous")), nil
 }
 ```
@@ -148,7 +148,7 @@ When you create a new module, FTL generates a schema that represents your code.
 
 ```schema
 module alice {
-  verb echo(String?) String
+  verb hello(String?) String
 }
 ```
 
@@ -189,7 +189,7 @@ And view your trace in the console:
 
 ### Create another module
 
-Create another module and call `alice.echo` from it with by importing the `alice` module and adding the verb client, `alice.EchoClient`, to the signature of the calling verb. It can be invoked as a function:
+Create another module and call `alice.hello` from it with by importing the `alice` module and adding the verb client, `alice.HelloClient`, to the signature of the calling verb. It can be invoked as a function:
 
 <Tabs groupId="languages">
   <TabItem value="go" label="Go" default>
@@ -199,7 +199,7 @@ Create another module and call `alice.echo` from it with by importing the `alice
 import "ftl/alice"
 
 //ftl:verb
-func Other(ctx context.Context, in string, ec alice.EchoClient) (string, error) {
+func Other(ctx context.Context, in string, ec alice.HelloClient) (string, error) {
     out, err := ec(ctx, in)
     ...
 }
@@ -213,15 +213,15 @@ package com.example
 
 import xyz.block.ftl.Export
 import xyz.block.ftl.Verb
-import ftl.alice.EchoClient
+import ftl.alice.Hellolient
 
 
 @Export
 @Verb
-fun other(req: String, echo: EchoClient): String = "Hello from Other , ${echo.call(req)}!"
+fun other(req: String, hello: HelloClient): String = "Hello from Other , ${hello.call(req)}!"
 ```
 
-Note that the `EchoClient` is generated by FTL and must be imported. Unfortunately at the moment JVM based languages have a bit of a chicken-and-egg problem with the generated clients. To force a dependency between the modules you need to add an import on a class that does not exist yet, and then FTL will generate the client for you. This will be fixed in the future.
+Note that the `HelloClient` is generated by FTL and must be imported.
 
   </TabItem>
   <TabItem value="java" label="Java">
@@ -231,19 +231,19 @@ package com.example.client;
 
 import xyz.block.ftl.Export;
 import xyz.block.ftl.Verb;
-import ftl.alice.EchoClient;
+import ftl.alice.HelloClient;
 
 public class OtherVerb {
 
     @Export
     @Verb
-    public String other(String request, EchoClient echoClient) {
-        return "Hello, " + echoClient.call(request) + "!";
+    public String other(String request, HelloClient helloClient) {
+        return "Hello, " + helloClient.call(request) + "!";
     }
 }
 ```
 
-Note that the `EchoClient` is generated by FTL and must be imported. Unfortunately at the moment JVM based languages have a bit of a chicken-and-egg problem with the generated clients. To force a dependency between the modules you need to add an import on a class that does not exist yet, and then FTL will generate the client for you. This will be fixed in the future.
+Note that the `HelloClient` is generated by FTL and must be imported.
 
   </TabItem>
   <TabItem value="schema" label="Schema">
@@ -252,16 +252,16 @@ When you create a second module that calls the first one, the schema would look
 
 ```schema
 module alice {
-  export verb echo(String?) String
+  export verb hello(String?) String
 }
 
 module other {
   export verb other(String) String
-    +calls alice.echo
+    +calls alice.hello
 }
 ```
 
-The `+calls` annotation in the schema indicates that the `other` verb calls the `echo` verb from the `alice` module.
+The `+calls` annotation in the schema indicates that the `other` verb calls the `hello` verb from the `alice` module.
 
   </TabItem>
 </Tabs>