Updating workaround (#91)

* Updating workaround

Signed-off-by: Sarah Ishida <sishida@us.ibm.com>

* Edits to text

Signed-off-by: Sarah Ishida <sishida@us.ibm.com>

* Updating text based on feedback

Signed-off-by: Sarah Ishida <sishida@us.ibm.com>

Author: sishida

docs/_documentations/troubleshooting.md

@@ -336,6 +336,8 @@ These steps reproduce the issue:
 5. In the **Output folder** field, copy and paste a path or edit the path directly.
 6. Click **Finish**. The OpenAPI generator fails if the folder doesn't already exist.
 
-**Workaround:** Manually create the output folder before you start the OpenAPI generator wizard. After you create the folder, you can start the wizard again.
+**Workaround:**
+- Manually create the output folder before you start the OpenAPI generator wizard. In the wizard, you can manually edit the **Output folder** text field. Ensure that the path points to a valid folder in the project.
+- Or you can use the **Browse...** button to select the folder that you want to use. The **Output folder** field is updated with the path.
 
 For post-client or post-server stub generation, use a separate output folder for code generation. Depending on the language and the generator type, the OpenAPI generator generates both source code files and build-related files. Some refactoring might be necessary. For example, if you are working with an existing Java or Maven project, move the generated source code to the proper source folder that already exists in the project. However, if your project is empty, the target output folder can be the root of the project, and you don't need to do as much refactoring and merging.