fix bug

src/en/guide/get_started/setup.md

@@ -9,14 +9,12 @@ configuration before use.
 
 We will take OpenAI API as an example to illustrate the full process, which applies identically to other LLM APIs.
 
-You can finish the setup by modifying the `config/config2.yaml`:
+You can finish the setup by modifying the [config2.yaml](https://github.com/geekan/MetaGPT/blob/main/config/config2.yaml):
 
 #### Use a config2.yaml
 
-1. In your current working directory, create a folder `config` and add a new file named `config2.yaml`
-   under it.
-2. Copy the content from the example [config2.yaml](https://github.com/geekan/MetaGPT/blob/main/config/config2.yaml) file
-   into your new files
+1. Run `metagpt --init-config  # create ~/.metagpt/config2.yaml, modify it to your own config`. This way you don't accidentally commit and share your API key using git.
+2. Take a look at [example](https://github.com/geekan/MetaGPT/blob/main/config/config2.yaml.example) and [code](https://github.com/geekan/MetaGPT/blob/main/metagpt/config2.py) to understand the configuration.  
 3. Fill in your own values to the file:
 
 ```yaml
@@ -25,10 +23,6 @@ llm:
   model: 'gpt-4-turbo-preview' # or gpt-3.5-turbo-1106 / gpt-4-1106-preview
 ```
 
-Remember: If you follow the `git clone` approach in [Installation](./installation), `config/config2.yaml` will already be
-there. Just edit it or make a copy named `~/.metagpt/config2.yaml` for editting. This way you don't accidentally commit and
-share your API key using git.
-
 > Note:
 > MetaGPT will read your setup in this priority order: `~/.metagpt/config2.yaml > config/config2.yaml`