Repository navigation
Overhaul for the linux-gaming article with Astro starlight features! - #1407
Alexander-Kendrick wants to merge 39 commits into
Conversation
Co-authored-by: Erin O'Connell <[email protected]>
Co-authored-by: Erin O'Connell <[email protected]>
… new content while updating old content.
Bumps the github-actions group with 5 updates: | Package | From | To | | --- | --- | --- | | [actions/checkout](https://github.com/actions/checkout) | `6` | `7` | | [actions/setup-node](https://github.com/actions/setup-node) | `6` | `7` | | [actions/cache](https://github.com/actions/cache) | `5` | `6` | | [xt0rted/markdownlint-problem-matcher](https://github.com/xt0rted/markdownlint-problem-matcher) | `1` | `3` | | [pnpm/action-setup](https://github.com/pnpm/action-setup) | `6.0.9` | `6.0.10` | Updates `actions/checkout` from 6 to 7 - [Release notes](https://github.com/actions/checkout/releases) - [Commits](actions/checkout@v6...v7) Updates `actions/setup-node` from 6 to 7 - [Release notes](https://github.com/actions/setup-node/releases) - [Commits](actions/setup-node@v6...v7) Updates `actions/cache` from 5 to 6 - [Release notes](https://github.com/actions/cache/releases) - [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md) - [Commits](actions/cache@v5...v6) Updates `xt0rted/markdownlint-problem-matcher` from 1 to 3 - [Release notes](https://github.com/xt0rted/markdownlint-problem-matcher/releases) - [Changelog](https://github.com/xt0rted/markdownlint-problem-matcher/blob/main/CHANGELOG.md) - [Commits](xt0rted/markdownlint-problem-matcher@v1...v3) Updates `pnpm/action-setup` from 6.0.9 to 6.0.10 - [Release notes](https://github.com/pnpm/action-setup/releases) - [Commits](pnpm/action-setup@0ebf471...0977fd9) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major dependency-group: github-actions - dependency-name: actions/setup-node dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major dependency-group: github-actions - dependency-name: actions/cache dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major dependency-group: github-actions - dependency-name: xt0rted/markdownlint-problem-matcher dependency-version: '3' dependency-type: direct:production update-type: version-update:semver-major dependency-group: github-actions - dependency-name: pnpm/action-setup dependency-version: 6.0.10 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: github-actions ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps the npm-all group with 9 updates in the / directory: | Package | From | To | | --- | --- | --- | | [@astrojs/markdown-satteri](https://github.com/withastro/astro/tree/HEAD/packages/markdown/satteri) | `0.3.5` | `0.4.2` | | [@astrojs/starlight](https://github.com/withastro/starlight/tree/HEAD/packages/starlight) | `0.41.7` | `0.42.5` | | [@iconify-json/simple-icons](https://github.com/iconify/icon-sets) | `1.2.93` | `1.2.98` | | [astro](https://github.com/withastro/astro/tree/HEAD/packages/astro) | `7.2.1` | `7.3.5` | | [astro-icon](https://github.com/natemoo-re/astro-icon/tree/HEAD/packages/core) | `1.1.5` | `1.2.0` | | [sharp](https://github.com/lovell/sharp) | `0.34.5` | `0.35.5` | | [@playwright/cli](https://github.com/microsoft/playwright-cli) | `0.1.18` | `0.1.22` | | [prettier](https://github.com/prettier/prettier) | `3.9.6` | `3.9.9` | | [prettier-plugin-astro](https://github.com/withastro/prettier-plugin-astro) | `0.14.1` | `1.1.0` | Updates `@astrojs/markdown-satteri` from 0.3.5 to 0.4.2 - [Release notes](https://github.com/withastro/astro/releases) - [Changelog](https://github.com/withastro/astro/blob/main/packages/markdown/satteri/CHANGELOG.md) - [Commits](https://github.com/withastro/astro/commits/@astrojs/[email protected]/packages/markdown/satteri) Updates `@astrojs/starlight` from 0.41.7 to 0.42.5 - [Release notes](https://github.com/withastro/starlight/releases) - [Changelog](https://github.com/withastro/starlight/blob/main/packages/starlight/CHANGELOG.md) - [Commits](https://github.com/withastro/starlight/commits/@astrojs/[email protected]/packages/starlight) Updates `@iconify-json/simple-icons` from 1.2.93 to 1.2.98 - [Commits](https://github.com/iconify/icon-sets/commits) Updates `astro` from 7.2.1 to 7.3.5 - [Release notes](https://github.com/withastro/astro/releases) - [Changelog](https://github.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md) - [Commits](https://github.com/withastro/astro/commits/[email protected]/packages/astro) Updates `astro-icon` from 1.1.5 to 1.2.0 - [Release notes](https://github.com/natemoo-re/astro-icon/releases) - [Changelog](https://github.com/natemoo-re/astro-icon/blob/main/packages/core/CHANGELOG.md) - [Commits](https://github.com/natemoo-re/astro-icon/commits/[email protected]/packages/core) Updates `sharp` from 0.34.5 to 0.35.5 - [Release notes](https://github.com/lovell/sharp/releases) - [Commits](lovell/sharp@v0.34.5...v0.35.5) Updates `@playwright/cli` from 0.1.18 to 0.1.22 - [Release notes](https://github.com/microsoft/playwright-cli/releases) - [Commits](microsoft/playwright-cli@v0.1.18...v0.1.22) Updates `prettier` from 3.9.6 to 3.9.9 - [Release notes](https://github.com/prettier/prettier/releases) - [Changelog](https://github.com/prettier/prettier/blob/main/CHANGELOG.md) - [Commits](prettier/prettier@3.9.6...3.9.9) Updates `prettier-plugin-astro` from 0.14.1 to 1.1.0 - [Release notes](https://github.com/withastro/prettier-plugin-astro/releases) - [Changelog](https://github.com/withastro/prettier-plugin-astro/blob/main/CHANGELOG.md) - [Commits](withastro/prettier-plugin-astro@v0.14.1...v1.1.0) --- updated-dependencies: - dependency-name: "@astrojs/markdown-satteri" dependency-version: 0.4.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: npm-all - dependency-name: "@astrojs/starlight" dependency-version: 0.42.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: npm-all - dependency-name: "@iconify-json/simple-icons" dependency-version: 1.2.97 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: npm-all - dependency-name: "@playwright/cli" dependency-version: 0.1.21 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: npm-all - dependency-name: astro dependency-version: 7.3.3 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: npm-all - dependency-name: astro-icon dependency-version: 1.2.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: npm-all - dependency-name: prettier dependency-version: 3.9.8 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: npm-all - dependency-name: prettier-plugin-astro dependency-version: 1.0.1 dependency-type: direct:development update-type: version-update:semver-major dependency-group: npm-all - dependency-name: sharp dependency-version: 0.35.4 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: npm-all ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps the github-actions group with 1 update in the / directory: [pnpm/action-setup](https://github.com/pnpm/action-setup). Updates `pnpm/action-setup` from 6.0.10 to 6.1.0 - [Release notes](https://github.com/pnpm/action-setup/releases) - [Commits](pnpm/action-setup@0977fd9...ea17c68) --- updated-dependencies: - dependency-name: pnpm/action-setup dependency-version: 6.1.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: github-actions ... Signed-off-by: dependabot[bot] <[email protected]>
Socialhappiness
left a comment
There was a problem hiding this comment.
Submitting Review up to line 156. Will continue tomorrow. Love this, great job!
Co-authored-by: Emma Truong <[email protected]>
Co-authored-by: Emma Truong <[email protected]>
Co-authored-by: Emma Truong <[email protected]>
Co-authored-by: Emma Truong <[email protected]>
Co-authored-by: Emma Truong <[email protected]>
Co-authored-by: Emma Truong <[email protected]>
Co-authored-by: Emma Truong <[email protected]>
Co-authored-by: Emma Truong <[email protected]>
Co-authored-by: Emma Truong <[email protected]>
Co-authored-by: Emma Truong <[email protected]>
Co-authored-by: Emma Truong <[email protected]>
Co-authored-by: Emma Truong <[email protected]>
Co-authored-by: Emma Truong <[email protected]>
Co-authored-by: Emma Truong <[email protected]>
Co-authored-by: Emma Truong <[email protected]>
Co-authored-by: Emma Truong <[email protected]>
Co-authored-by: Emma Truong <[email protected]>
Co-authored-by: Emma Truong <[email protected]>
Co-authored-by: Emma Truong <[email protected]>
Co-authored-by: Emma Truong <[email protected]>
Co-authored-by: Emma Truong <[email protected]>
Co-authored-by: Emma Truong <[email protected]>
Socialhappiness
left a comment
There was a problem hiding this comment.
up to line 379! In general, it's not necessary to use I, you, we or our in technical documentation. Adjectives and adverbs should be used sparingly if at all.
| ``` | ||
|
|
||
| Now, let's install `protonup` via `pip`. | ||
| With pipx installed, we now need to ensure that the location pipx is going to be installing our programs is included in our **PATH**. This will allow us to launch applications in the terminal by simply typing their names in and our terminal will understand what we're trying to run. |
There was a problem hiding this comment.
| With pipx installed, we now need to ensure that the location pipx is going to be installing our programs is included in our **PATH**. This will allow us to launch applications in the terminal by simply typing their names in and our terminal will understand what we're trying to run. | |
| Confirm the location pipx is going to be installing programs in is included in your **PATH**. This enables the ability to launch applications in the terminal by simply typing their names and the terminal will understand what you're trying to run. To confirm the location, run the following command; |
modified wording to remove the 'we' type references
| pipx ensurepath | ||
| ``` | ||
|
|
||
| Once you've ran that command, you'll need to close the terminal and launch it once more for the changes to take effect. With **pipx ensurepath** having been ran, we should now be able to install protonup and run it without issues. |
There was a problem hiding this comment.
| Once you've ran that command, you'll need to close the terminal and launch it once more for the changes to take effect. With **pipx ensurepath** having been ran, we should now be able to install protonup and run it without issues. | |
| Close the terminal and launch it once more for the changes to take effect. |
I think this is unnecessary because you explained why we're running that command before running the command, so it doesn't need an after explanation too imo.
| Once you've ran that command, you'll need to close the terminal and launch it once more for the changes to take effect. With **pipx ensurepath** having been ran, we should now be able to install protonup and run it without issues. | ||
|
|
||
| The `protonup` command will be available after a reboot, or you can run the below command to add it to your `PATH` for immediate use. | ||
| Now, let's install **protonup** via **pipx**. |
There was a problem hiding this comment.
| Now, let's install **protonup** via **pipx**. | |
| Install **protonup** via **pipx** with the following command: |
| #### Manage ProtonGE with Protonup | ||
|
|
||
| After <u>Steam</u> is installed, you can run protonup in a terminal. The command will fetch the newest ProtonGE build. This tool will also pull hotfixes. Below is an example of the tools output: | ||
| After **Steam** is installed, you can run protonup in a terminal. The command will fetch the newest ProtonGE build. This tool will also pull hotfixes. Below is an example of the tools output: |
There was a problem hiding this comment.
| After **Steam** is installed, you can run protonup in a terminal. The command will fetch the newest ProtonGE build. This tool will also pull hotfixes. Below is an example of the tools output: | |
| After **Steam** is installed, run **protonup** in a terminal to fetch the newest ProtonGE build. This tool will also pull hotfixes. Below is an example of the tools output: |
|
|
||
| If you'd like something a little prettier than the default view, we suggest setting your interface to either **Covers** or **Carrousel** mode, starting up Faugus in either **Maximized** or **Fullscreen**, changing the Position of your games to **Bottom**, then setting the checkboxes under **Display** for **Labels**, **Banner**, and **Overview** on. We suggest leaving **Overview** off though if you're using **Covers** view mode. If you have an API Key added, you can then click OK to save your interface and you will get a view that heavily showcases artwork for your games. | ||
|
|
||
| There's other views you can set up too, experiment with what looks nice for you or leave the default settings. |
There was a problem hiding this comment.
| There's other views you can set up too, experiment with what looks nice for you or leave the default settings. | |
| Below are examples of different types of views you can customize. |
|
|
||
| ### Adding a Windows Game | ||
|
|
||
| Now that we have Faugus set up the way we want it, we can add our first game. |
There was a problem hiding this comment.
| Now that we have Faugus set up the way we want it, we can add our first game. | |
| Now that Faugus is set up, it's time to add the first game. |
|
|
||
| Faugus can be used to launch multiple kinds of games, both Windows and Linux. | ||
|
|
||
| Let's start by clicking the Add Game button from the main interface. This is signified with a **+** icon. |
There was a problem hiding this comment.
| Let's start by clicking the Add Game button from the main interface. This is signified with a **+** icon. | |
| Start by clicking the Add Game button from the main interface. This is signified with a **+** icon. |
|
|
||
|  | ||
|
|
||
| We're going to install a Windows Game. In the New Game/App menu, let's give our game a name. This name you enter will be used to scrape the artwork from **steamgrid.db**. This happens regardless of if you added an API Key or not. |
There was a problem hiding this comment.
| We're going to install a Windows Game. In the New Game/App menu, let's give our game a name. This name you enter will be used to scrape the artwork from **steamgrid.db**. This happens regardless of if you added an API Key or not. | |
| In the New Game/App menu, give the game a name. This name you enter will be used to scrape the artwork from **steamgrid.db**. This happens regardless of if you added an API Key or not. |
we're in the section about installing a windows game, so I removed that first sentence
| We're going to install a Windows Game. In the New Game/App menu, let's give our game a name. This name you enter will be used to scrape the artwork from **steamgrid.db**. This happens regardless of if you added an API Key or not. | ||
|
|
||
| <Aside type="tip" title="Scraping Artwork"> | ||
| If you've integrated SteamGridDB into Faugus, it'll suggest game names based on results from the website as you type. You also should be able to simply left click the banner and Cover artwork fields to freely select artwork that is to your liking. |
There was a problem hiding this comment.
| If you've integrated SteamGridDB into Faugus, it'll suggest game names based on results from the website as you type. You also should be able to simply left click the banner and Cover artwork fields to freely select artwork that is to your liking. | |
| If SteamGridDB is integrated into Faugus, it'll suggest game names based on results from the website as you type. Left click the banner and cover artwork fields to freely select artwork. |
Co-authored-by: Emma Truong <[email protected]>
Socialhappiness
left a comment
There was a problem hiding this comment.
Excellent job Alex!
I'm going to submit this review and request those changes be made, but definitely let me know if you disagree!
For the remaining lines after 686, can you please go through and see if there's any opportunity to change the words "you" "we" "our" to "the", please update! Remove any areas where the word 'simply' or 'just' is used.
The instructions are great, it's just a little like you're talking in a support ticket, so trying to help edit it toward more support doc style. Very proud of you for this!
| If an API Key was not added, you can still right click the cover art and Refresh it, grabbing new art from your game's name, or select artwork that you're providing instead. You will not be able to select a banner since that field will be missing. | ||
| </Aside> | ||
|
|
||
| Our Path is where we select the path to the game's executable. This is what Faugus is launching when you click **Play** in the Faugus Launcher. For a Windows game, this will be our **.exe** application. Simply click the **searchglass icon** and pick your **executable application**. Faugus allows you to either select the **.exe** if it's already ready to play, or run a **setup.exe installer** which will run the installer of the game and then change the executable to your game's executable, all while also setting up the Prefix for you. If you run an installer, everything is set up automatically for you. |
There was a problem hiding this comment.
| Our Path is where we select the path to the game's executable. This is what Faugus is launching when you click **Play** in the Faugus Launcher. For a Windows game, this will be our **.exe** application. Simply click the **searchglass icon** and pick your **executable application**. Faugus allows you to either select the **.exe** if it's already ready to play, or run a **setup.exe installer** which will run the installer of the game and then change the executable to your game's executable, all while also setting up the Prefix for you. If you run an installer, everything is set up automatically for you. | |
| Our Path is where we select the path to the game's executable. This is what Faugus is launching when you click **Play** in the Faugus Launcher. For a Windows game, this will be our **.exe** application. Simply click the **magnifying glass icon** and pick your **executable application**. Faugus allows you to either select the **.exe** if it's already ready to play, or run a **setup.exe installer** which will run the installer of the game, change the executable to your game's executable, and also set up the Prefix for you. If you run an installer, everything is set up automatically for you. |
| <Aside type="caution" icon="bars" title="Options for Installing a Game"> | ||
| <Tabs> | ||
| <TabItem label="Select an Executable"> | ||
| This is the option you're going to want to pick if your game launches from just a **.exe** or if you've already installed the game and are adding it to Faugus. Simply navigate to where your Executable file is stored and select it. Now when you launch the game, it will launch this Executable that is associated with it. The Icon for Faugus will generally pull the Executable icon automatically. |
There was a problem hiding this comment.
| This is the option you're going to want to pick if your game launches from just a **.exe** or if you've already installed the game and are adding it to Faugus. Simply navigate to where your Executable file is stored and select it. Now when you launch the game, it will launch this Executable that is associated with it. The Icon for Faugus will generally pull the Executable icon automatically. | |
| This is the option you're going to want to pick if your game launches from an **.exe** or if you've already installed the game and are adding it to Faugus. Navigate to where your executable file is stored and select it. Now when you launch the game, it will launch this executable that is associated with it. The icon for Faugus will generally pull the executable icon automatically. |
| This is the option you're going to want to pick if your game launches from just a **.exe** or if you've already installed the game and are adding it to Faugus. Simply navigate to where your Executable file is stored and select it. Now when you launch the game, it will launch this Executable that is associated with it. The Icon for Faugus will generally pull the Executable icon automatically. | ||
|
|
||
| <Aside type="note" title="Storing your Game Inside of a Prefix when Selecting an Executable"> | ||
| When you install a game from an installer, the executable is installed inside of the Prefix, making it where the Prefix and Game Files are all together. This is not the case if you select an executable by default and it can lead to the location of the games differing depending on the installation method you choose in Faugus. |
There was a problem hiding this comment.
| When you install a game from an installer, the executable is installed inside of the Prefix, making it where the Prefix and Game Files are all together. This is not the case if you select an executable by default and it can lead to the location of the games differing depending on the installation method you choose in Faugus. | |
| When you install a game from an installer, the executable is installed inside of the prefix, which is where the game files are stored. If you select an executable by default, it can lead to the location of the games differing, depending on the installation method you choose in Faugus. |
| <Aside type="note" title="Storing your Game Inside of a Prefix when Selecting an Executable"> | ||
| When you install a game from an installer, the executable is installed inside of the Prefix, making it where the Prefix and Game Files are all together. This is not the case if you select an executable by default and it can lead to the location of the games differing depending on the installation method you choose in Faugus. | ||
|
|
||
| If you would like to generate the Prefix so you can move your game inside of the Prefix, you should point to an executable that won't launch. Typing in something such as **null** in the **Path** text field is enough to make it where Faugus will generate your Prefix without actually launching anything when you click the **Play button** on your game. Fill out the title, **null** the path, and pick a Prefix location if the default isn't where you want to store it, then click **Ok** to save the game. Your game will show it's artwork in greyscale, which indicates that your executable is not found. Since we put **null**, that'd be expected. |
There was a problem hiding this comment.
| If you would like to generate the Prefix so you can move your game inside of the Prefix, you should point to an executable that won't launch. Typing in something such as **null** in the **Path** text field is enough to make it where Faugus will generate your Prefix without actually launching anything when you click the **Play button** on your game. Fill out the title, **null** the path, and pick a Prefix location if the default isn't where you want to store it, then click **Ok** to save the game. Your game will show it's artwork in greyscale, which indicates that your executable is not found. Since we put **null**, that'd be expected. | |
| If you would like to generate the prefix so you can move your game inside of the prefix, you should point to an executable that won't launch. Typing in something such as **null** in the **Path** text field is enough to make Faugus generate your prefix without actually launching anything when you click the **Play button** on your game. Fill out the title, **null** the path, and pick a prefix location if the default isn't where you want to store it. Click **Ok** to save the game. Your game will show it's artwork in greyscale, which indicates that your executable is not found. Since we put **null**, that is expected behavior. |
|  | ||
|
|
||
| Open the <u>Pop!_Shop</u> application then either search for GameHub, or navigate to the GameHub page by clicking the <u>GameHub</u> icon on the Pop!_Shop home page. Now click the **Install** button. | ||
| If you set the path to something that won't launch and click the **Play Button** it will generate your Prefix. After that's done, make sure you move the game files into the Prefix after it's been generated. Then we need to set your **Path** to now point at your game's Executable. This is done by right clicking the game, and select **Edit** so you can change the executable to your **game.exe** after moving it into the newly made Prefix. |
There was a problem hiding this comment.
| If you set the path to something that won't launch and click the **Play Button** it will generate your Prefix. After that's done, make sure you move the game files into the Prefix after it's been generated. Then we need to set your **Path** to now point at your game's Executable. This is done by right clicking the game, and select **Edit** so you can change the executable to your **game.exe** after moving it into the newly made Prefix. | |
| If the path is set to something that won't launch, clicking the **Play Button** will generate your prefix. After the prefix is generated, move the game files into the prefix . Set your **Path** to point at your game's executable. Right click the game, select **Edit** and change the executable to the **game.exe**. |
| <Aside type="caution" icon="bars" title="Options for Install Scripts"> | ||
| <Tabs> | ||
| <TabItem label="Installing from within Lutris"> | ||
| After clicking the **+** icon in the top left corner to add a new game, you'll be greeted by the various options you have to add games into Lutris. You will want to select **Search the Lutris Website for Installers** to search lutris.net from within the application without ever needing to open a web browser. |
There was a problem hiding this comment.
| After clicking the **+** icon in the top left corner to add a new game, you'll be greeted by the various options you have to add games into Lutris. You will want to select **Search the Lutris Website for Installers** to search lutris.net from within the application without ever needing to open a web browser. | |
| After clicking the **+** icon in the top left corner to add a new game, the various options to add games into Lutris will be displayed. Select **Search the Lutris Website for Installers** to search lutris.net from within the application without needing to open a web browser. |
|
|
||
|  | ||
|
|
||
| Once you click on that button, you'll need to run a search for what you want to install. This will show all relevant options related to your search. Simply select the game you are installing from the list. |
There was a problem hiding this comment.
| Once you click on that button, you'll need to run a search for what you want to install. This will show all relevant options related to your search. Simply select the game you are installing from the list. | |
| Run a search for what you want to install. This will show all relevant options related to your search. Select the game you are installing from the list. |
|
|
||
|  | ||
|
|
||
| From there, you'll be greeted with all the versions of World of Warcraft that lutris.net has installation scripts for. These scripts are all maintained by the community and users like yourself. If you're having trouble with one, you should look on lutris.net for the game page and see if the script is out of date or if it offers specialized instructions. In our example, we'll be installing the first option for Battle.net's standard version of World of Warcraft by clicking **Install**. |
There was a problem hiding this comment.
| From there, you'll be greeted with all the versions of World of Warcraft that lutris.net has installation scripts for. These scripts are all maintained by the community and users like yourself. If you're having trouble with one, you should look on lutris.net for the game page and see if the script is out of date or if it offers specialized instructions. In our example, we'll be installing the first option for Battle.net's standard version of World of Warcraft by clicking **Install**. | |
| From there, all the versions of World of Warcraft that lutris.net has installation scripts for will be displayed. These scripts are maintained by the community and users like yourself. If you're having trouble with one, you can look on lutris.net for the game page and see if the script is out of date or if it offers specialized instructions. In our example, we'll be installing the first option for Battle.net's standard version of World of Warcraft by clicking **Install**. |
| </TabItem> | ||
|
|
||
| <TabItem label="Installing from lutris.net"> | ||
| If we're installing from lutris.net, simply select the **Install** button on the version of World of Warcraft to install. We are installing the Battle.net version, so we will click that. |
There was a problem hiding this comment.
| If we're installing from lutris.net, simply select the **Install** button on the version of World of Warcraft to install. We are installing the Battle.net version, so we will click that. | |
| If we're installing from lutris.net, select the **Install** button on the version of World of Warcraft to install. This example will install the Battle.net version. |
|
|
||
|  | ||
|
|
||
| Once you have done so, this will launch Lutris if it isn't running and open the installer dialog for Lutris associated with this script. Because we selected the script, it will only show the install button for specifically the script you selected from the website. |
There was a problem hiding this comment.
| Once you have done so, this will launch Lutris if it isn't running and open the installer dialog for Lutris associated with this script. Because we selected the script, it will only show the install button for specifically the script you selected from the website. | |
| Lutris will launch if it isn't running and open the installer dialog associated with the selected script. Because we selected the script, it will only show the install button for the specific script selected on the website. |
Socialhappiness
left a comment
There was a problem hiding this comment.
Excellent job Alex!
I'm going to submit this review and request those changes be made, but definitely let me know if you disagree!
For the remaining lines after 686, can you please go through and see if there's any opportunity to change the words "you" "we" "our" to "the", please update! Remove any areas where the word 'simply' or 'just' is used.
The instructions are great, it's just a little like you're talking in a support ticket, so trying to help edit it toward more support doc style. Very proud of you for this!
Drastically overhauled our gaming article, adding Astro features, new content, updated old content, included section on Lutris, and more.
I've given it a single pass through for proofreading, it is a sizable article now that will likely take some time to go over.