updated export section

Author: ganesh-bruno

public/screenshots/open-api/export-api-spec.webp

@@ -14,23 +14,22 @@ Before exporting a collection, ensure:
 - Your collection is properly organized with clear request structures
 - All endpoints have appropriate HTTP methods defined
 - Request parameters and headers are properly configured
-- Response examples are included where possible
-
-## Export Methods
-
-1. **File Export**: Export to a local OpenAPI specification file
-
 
 ### Exporting to a File
 
 1. Open Bruno and navigate to your collection
 2. Click on the context menu (three dots) in the collections panel
 3. Select **Share** from the dropdown menu
+
+![collection-settings](/screenshots/git-integration/share-collection/1-share-collection-overview.webp)
+
 4. Choose **OpenAPI Specification** option
+
+![ExportModal](/screenshots/get-started/import-export/export_collection/2-export-options.webp)
+
 5. Enter name of your file and location.
 6. Click **Create**
 
-![export-openapi-file](/screenshots/open-api/export-api-spec.webp)
 
 ## Example Exported Structure
 

src/pages/open-api/exportOAS.mdx

@@ -36,12 +36,9 @@ Bruno offers two ways to import OpenAPI specifications:
 
 ### Importing from a URL
 
-1. Open Bruno and navigate to your workspace
-2. Click on the context menu (three dots) in the collections panel
-3. Select **Import** from the dropdown menu
-4. Choose **OpenAPI V3 URL** option
-5. Enter the URL of your OpenAPI specification
-6. Click **Import** to create the collection
+The import method for URL option is same as for URL but you need to select **OpenAPI V3 URL** as option and provide URL of OAS file which is publically available. 
+
+After, Importing the OAS file the sample collection will looks like this.
 
 ![import-collection-oas](/screenshots/open-api/import-collection-oas.webp)