Address formatting baseline review feedback.

Reduce editorconfig duplication, add Go/Makefile tab alignment and max line length, and tighten README wording to avoid config drift and clarify .editorconfig recommendation.

Author: benzekrimaha

.editorconfig

@@ -5,23 +5,15 @@ charset = utf-8
 end_of_line = lf
 insert_final_newline = true
 trim_trailing_whitespace = true
-
-[*.{js,jsx,ts,tsx}]
-indent_style = space
-indent_size = 4
-
-[*.{json}]
 indent_style = space
 indent_size = 4
+max_line_length = 120
 
 [*.{yml,yaml}]
 indent_style = space
 indent_size = 2
 
-[*.md]
-indent_style = space
-indent_size = 4
-
-[Makefile]
+[{Makefile,*.go,go.*}]
 indent_style = tab
+indent_size = 4
 

README.md

@@ -46,23 +46,12 @@ To use it in a project:
    }
    ```
 
-Projects are free to override options locally (for example `tabWidth` or
+Projects may override options locally (for example `tabWidth` or
 `printWidth`) if they have strong legacy constraints, but this configuration
 is intended to be the **default Scality baseline** for new or reformatted
-Node.js codebases. YAML defaults to 2-space indentation, JSON and Markdown to
-4-space indentation, and Markdown prose is left un-reflowed by default
-(`proseWrap: 'preserve'`) to avoid noisy diffs in existing documentation.
-
-## Editor configuration
-
-For a consistent editor experience, you can copy or adapt the `.editorconfig`
-from this repository. It aligns with the ESLint and Prettier baselines:
-
-- **JS/TS**: spaces with 4-space indentation.
-- **JSON/Markdown**: spaces with 4-space indentation.
-- **YAML**: spaces with 2-space indentation.
-- `end_of_line = lf`, `insert_final_newline = true`,
-  `trim_trailing_whitespace = true`.
+Node.js codebases. YAML/JSON/Markdown files default to a 2-space indentation
+and Markdown prose is left un-reflowed by default (`proseWrap: 'preserve'`),
+to avoid noisy diffs in existing documentation.
 
 ## Contributing