From 734a982689a8c5528f5f2b6a075d2797f381095c Mon Sep 17 00:00:00 2001 From: wish Date: Sat, 2 Mar 2024 21:37:25 +1100 Subject: [PATCH] proofreading --- AUTHORS.md | 19 ++++++++++--------- README.md | 12 ++++++------ 2 files changed, 16 insertions(+), 15 deletions(-) diff --git a/AUTHORS.md b/AUTHORS.md index 618d34264..5617c5308 100644 --- a/AUTHORS.md +++ b/AUTHORS.md @@ -1,29 +1,30 @@ -# List of AUTHORS who contributed over time to the Erupe project +# List of authors who contributed to Erupe ## Point of current development The project is currently developed under https://github.com/ZeruLight/Erupe ## History of development Development of this project dates back to 2019, and was developed under various umbrellas over time: -* Cappuccino (Fist/Ando/Ellie42) (The Erupe Developers), 2019-2020 (https://github.com/Ellie42/Erupe / https://github.com/ricochhet/Erupe-Legacy) (Still active closed source) +* Cappuccino (Fist/Ando/Ellie42) ("The Erupe Developers"), 2019-2020 (https://github.com/Ellie42/Erupe / https://github.com/ricochhet/Erupe-Legacy) (Still active closed source) * Einherjar Team, ????-2022 Feb (There is no git history for this period, this team's work was taken and used as a foundation for future repositories) * Community Edition, 2022 (https://github.com/xl3lackout/Erupe) -* Zerulight, 2022-2023 (https://github.com/ZeruLight/Erupe) +* sekaiwish Fork, 2022 (https://github.com/sekaiwish/Erupe) +* ZeruLight, 2022-2023 (https://github.com/ZeruLight/Erupe) ## Authorship of the code Authorship is assigned for each commit within the git history, which is stored in these git repos: * https://github.com/ZeruLight/Erupe -* https://github.com/Ellie42/Erupe +* https://github.com/Ellie42/Erupe * https://github.com/ricochhet/Erupe-Legacy * https://github.com/xl3lackout/Erupe - -Note there is a divergence between Ellie42s branch and xl3lackout where history has been lost. -Unfortunately, we have no detailed information on the history of the Erupe pre-2022 -if somebody can provide information, please contact us, so that we can make this history available. +Note the divergence between Ellie42's branch and xl3lackout's where history has been lost. + +Unfortunately, we have no detailed information on the history of Erupe before 2022. +If somebody can provide information, please contact us, so that we can make this history available. ## Exceptions with third-party libraries The third-party libraries have their own way of addressing authorship and the authorship of commits importing/updating a third-party library reflects who did the importing instead of who wrote the code within the commit. -The Authors of third-party libraries are not explicitly mentioned, and usually is possible to obtain from the files belonging to the third-party libraries. \ No newline at end of file +The authors of third-party libraries are not explicitly mentioned, and usually is possible to obtain from the files belonging to the third-party libraries. \ No newline at end of file diff --git a/README.md b/README.md index b9be1fb05..8ac37b22b 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ # Erupe -## Client Compatiblity +## Client Compatibility ### Platforms - PC - PlayStation 3 @@ -34,15 +34,15 @@ If you want to modify or compile Erupe yourself, please read on. ## Docker -Please see the readme in [docker/README.md](./docker/README.md). At the moment this is only really good for quick installs and checking out development not for production. +Please see [docker/README.md](./docker/README.md). This is intended for quick installs and development, not for production. ## Schemas We source control the following schemas: -- Initialisation Schemas: These initialise the application database to a clean install from a specific version. -- Update Schemas: These are update files they should be ran in order of version to get to the latest schema. -- Patch Schemas: These are for development and should be ran from the lastest available update schema or initial schema. These eventually get condensed into `Update Schemas` and then deleted when updated to a new version. -- Bundled Schemas: These are demo reference files to allow servers to be able to roll their own shops, distributions gachas and scenarios set ups. +- Initialization Schema: This initializes the application database to a specific version (9.1.0). +- Update Schemas: These are update files that should be ran on top of the initialization schema. +- Patch Schemas: These are for development and should be run after running all initialization and update schema. These get condensed into `Update Schemas` and deleted when updated to a new release. +- Bundled Schemas: These are demo reference files to give servers standard set-ups. Note: Patch schemas are subject to change! You should only be using them if you are following along with development.