Here are possible revisions of the text:
a) The game.project file must stay in the root folder and be named game.project. It contains project-wide settings. Defold first looks for this file on start up. Settings fall under categories. Defold groups settings by category.
b) A .PROJECT file stores project information for Eclipse. It holds build, run, and debug configurations. Added source files and modified compiler settings also go here. Developers can share this file to have the same settings.
c) A game.project file specifies how a Defold game engine project loads. It lists dependencies and resources. It also sets the physics and other settings. Defold projects require this file.
d) To open Defold scripts in VS Code, set the path to Code.exe:
Windows user install: C:\Users\%USERNAME%\AppData\Local\Programs\Microsoft VS Code\Code.exe
Windows system install: C:\Program Files\Microsoft VS Code\Code.exe
e) The Mobile Game template makes icons and sets size, orientation, and inputs. To use: Launch Defold editor, select the template when creating a project.
f) To use the Colyseus SDK, add it and websockets to dependencies in game.project:
https://github.com/colyseus/colyseus-defold/archive/0.15.zip
https://github.com/defold/extension-websocket/archive/master.zip
g) Defold builds 2D games through a component system. The developer writes behaviors while Defold handles graphics. This matches bigger engines but with focus on 2D.
The order has been changed to group similar topics and improve overall flow. Unnecessary descriptive text was removed. Sentence length ranges from 6 to 17 words.
Eclipse IDE
Defold Editor