Apply suggestions from code review

Co-authored-by: Stefan Dirix <[email protected]>

Author: LukasBoll

content/docs/tutorial/dynamic-enum.mdx

@@ -15,8 +15,7 @@ This approach allows you to build flexible and interactive forms that adapt to u
 Imagine a form where users need to provide their location by selecting a country, a region and a city.
 The options for countries and regions are fetched from an API.
 The available regions depend on the selected country.
-To address those requirements, we'll create custom renderers for the country and region.
-The example is also implemented in the [react-seed](https://github.com/eclipsesource/jsonforms-react-seed) app.
+To address those requirements, we'll create custom renderers for country and region.
 
 <WithRegionRenderer />
 
@@ -26,7 +25,7 @@ The example is also implemented in the [react-seed](https://github.com/eclipseso
 To begin, let's introduce the corresponding JSON schema.
 We have created an object with properties for country, region, and city.
 In our example, the schema also includes a property `x-url`, which specifies the entry point of the corresponding API.
-Both `country` and `region` have a property `endpoint`, indicating the endpoint from which the data should be fetched.
+Both `country` and `region` have a property `x-endpoint`, indicating the endpoint from which the data should be fetched.
 Additionally, they have a field specifying which fields depend on the input.
 In the case of the `country` field, the `region` and `city` fields depend on it and will get reset, if the value of the `country` changes.
 The `city` field, in turn, is dependent on the `region` field.
@@ -84,7 +83,7 @@ const App = () =>{
 
 ### The Country Renderer
 
-The core of the country renderer is a dropdown, we can reuse the MaterialEnumControl from the material-renderer set.
+The core of the country renderer is a dropdown, therefore we can reuse the MaterialEnumControl from the React Material renderer set.
 To reuse material renderers, the Unwrapped renderers must be used. (more information regarding reusing renderers can be seen [here](./custom-renderers#reusing-existing-controls))
 
 ```js
@@ -120,7 +119,7 @@ Changing the context's value will trigger a re-render of components that use it,
 #### Accessing Schema Data
 
 The `endpoint` and `dependent` fields can be obtained from the schema object provided to the custom renderer via JSON Forms.
-Since these fields are not part of the standard JSON schema type in JSON Forms, we must add them to the schema´s interface and access them as follows:
+Since these fields are not part of the standard JSON schema type in JSON Forms, we must add them to the schema's interface and access them as follows:
 
 ```js
 type JsonSchemaWithDependenciesAndEndpoint = JsonSchema & {
@@ -142,7 +141,7 @@ export const Country = (
 #### The Country Renderer
 
 The country renderer uses the `APIContext` to query the API and fetch the available options.
-We utilize the `useEffect` hook to reload new options, if API changes.
+We utilize the `useEffect` hook to initialize the options.
 While waiting for the API response, we set the available options to empty and display a loading spinner.
 In the `handleChange` function, we set the new selected value and reset all dependent fields;
 When changing the country, both the region and city will be reset to `undefined`.
@@ -169,11 +168,10 @@ export const Country = (
   const dependent: string[] = schema.dependent ? schema.dependent : [];
 
   useEffect(() => {
-    setOptions([]);
     api.get(endpoint).then((result) => {
       setOptions(result);
     });
-  }, [api, endpoint]);
+  }, []);
 
   if (options.length === 0) {
     return <CircularProgress />;