docs: clean up README formatting and improve readability

- Removed unnecessary blank lines and adjusted formatting in the main README and the Type Generation Command documentation to enhance clarity and consistency.
- Ensured proper alignment of bullet points for better visual presentation.

Author: alvarosabu

README.md

@@ -94,7 +94,6 @@ Then you can set breakpoints directly to the typescript files and the debugger w
 
 ![Debugging](/.github/assets/breakpoints.png)
 
-
 ## Community
 
 For help, discussion about best practices, or any other conversation that would benefit from being searchable:
@@ -112,9 +111,9 @@ For bugs or feature requests, please [submit an issue](https://github.com/storyb
 > [!IMPORTANT]
 > Please search existing issues before submitting a new one. Issues without a minimal reproducible example will be closed. [Why reproductions are Required](https://antfu.me/posts/why-reproductions-are-required).
 
-### I can't share my company project code 
+### I can't share my company project code
 
-We understand that you might not be able to share your company's project code. Please provide a minimal reproducible example that demonstrates the issue by using tools like [Stackblitz](https://stackblitz.com) or a link to a Github Repo lease make sure you include a README file with the instructions to build and run the project, important not to include any access token, password or personal information of any kind. 
+We understand that you might not be able to share your company's project code. Please provide a minimal reproducible example that demonstrates the issue by using tools like [Stackblitz](https://stackblitz.com) or a link to a Github Repo lease make sure you include a README file with the instructions to build and run the project, important not to include any access token, password or personal information of any kind.
 
 ### I only have a question
 

src/commands/types/generate/README.md

@@ -57,14 +57,14 @@ typesCommand
   });
 
 // 2. Operations Layer (actions.ts)
-  - generateTypes()
-  - generateStoryblokTypes()
-  - saveTypesToFile()
+-generateTypes()
+- generateStoryblokTypes()
+- saveTypesToFile()
 
 // 3. Actions Layer (actions.ts)
-  - getComponentType()
-  - getComponentPropertiesTypeAnnotations()
-  - sanitizeComponentName()
+- getComponentType()
+- getComponentPropertiesTypeAnnotations()
+- sanitizeComponentName();
 ```
 
 ### Processing Flow Examples
@@ -179,12 +179,12 @@ Flow:
 for (const component of spaceData.components) {
   const componentType = getComponentType(component.name, options);
   const properties = getComponentPropertiesTypeAnnotations(component.schema, options);
-  
+
   // 2. Create a separate file for each component
   const fileContent = `export interface ${componentType} {
   ${properties}
 }`;
-  
+
   // 3. Save to a separate file
   await saveToFile(`${component.name}.d.ts`, fileContent);
 }
@@ -317,4 +317,4 @@ The command includes comprehensive test coverage:
 **Error Handling**
 - [ ] It should throw an error if the space is not provided: "Please provide the space as argument --space YOUR_SPACE_ID."
 - [ ] It should handle errors during type generation gracefully
-- [ ] It should provide meaningful error messages for common issues 
+- [ ] It should provide meaningful error messages for common issues