Skip to content

Commit 3d3317f

Browse files
authored
Correct capitalization of "GitHub" (#194)
1 parent 3fc2f3b commit 3d3317f

File tree

5 files changed

+5
-5
lines changed

5 files changed

+5
-5
lines changed

content/docs/installation/installation-linux.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ download a development version from [here](../development-build) or use AUR if y
5252
2. In rolling-release distros (e.g Arch, Solus), you can expect to get the recent version of Flameshot within the first few days of release, but in nonrolling-release distros (e.g Ubuntu, Debian, Fedora) you will most probably stay a few versions behind, especially if your Linux release version is old (check [here](https://repology.org/metapackage/flameshot/versions)). In these cases you might want to either go for the packages we provide on [Flameshot release page](https://github.com/flameshot-org/flameshot/releases) or go with distro-agnostic solutions which are explained [here](#distro-agnostic).
5353

5454

55-
In addition, we also have continuous integration, it currently provides the following packages which can be accessed via our [Github release page](https://github.com/flameshot-org/flameshot/releases):
55+
In addition, we also have continuous integration, it currently provides the following packages which can be accessed via our [GitHub release page](https://github.com/flameshot-org/flameshot/releases):
5656

5757
- Debian10 (buster)
5858
- Ubuntu18.04 (bionic)

content/docs/installation/installation-osx.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ You can install Flameshot on [macOS](https://en.wikipedia.org/wiki/MacOS) using
2828
>
2929
> After following all those steps above, flameshot will open without problems in your Mac.
3030
- Download DMG file:
31-
1. Navigate to [the release page on Github](https://github.com/flameshot-org/flameshot/releases)
31+
1. Navigate to [the release page on GitHub](https://github.com/flameshot-org/flameshot/releases)
3232
2. From the assets of the latest stable release, download the latest DMG file
3333
3. Double-click on the DMG file you downloaded
3434
4. Drag and drop the `flameshot.app` to your `/Applications` folder

content/docs/installation/installation-windows.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ choco install flameshot
5555
### Manual installation
5656

5757
If you want to manually download and install the Windows version, you have to follow these steps:
58-
1. Go to [the latest release on out Github repo](https://github.com/flameshot-org/flameshot/releases/latest)
58+
1. Go to [the latest release on out GitHub repo](https://github.com/flameshot-org/flameshot/releases/latest)
5959
![](/media/content/docs/installation/installation-windows/2023-06-28_13-45_go_to_latest_release.png)
6060
2. Scroll down to find the "Assets" as shown in the picture below (it might be collapsed, so click on the triangle on the left side to open it)
6161
![](/media/content/docs/installation/installation-windows/2023-06-28_13-46_go_to_assets.png)

content/docs/installation/source-code.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -90,7 +90,7 @@ pacman -S xdg-desktop-portal xdg-desktop-portal-wlr grim
9090

9191
## Getting the Source Code
9292

93-
You can get the source code from [our Github repository](https://github.com/flameshot-org/flameshot). Either clone the repository or download a ZIP file. We suggest downloading the ZIP file if you want to build on specific version, but if you want to build different commits and versions, using `git` makes it much easier.
93+
You can get the source code from [our GitHub repository](https://github.com/flameshot-org/flameshot). Either clone the repository or download a ZIP file. We suggest downloading the ZIP file if you want to build on specific version, but if you want to build different commits and versions, using `git` makes it much easier.
9494
Please note that in this page we explain how to download the [master branch](https://github.com/flameshot-org/flameshot/tree/master), but you can get the source code for every [Pull Request](https://github.com/flameshot-org/flameshot/pulls) and compile them if you like to.
9595

9696
In general we suggest you to create a temporary directory to download the file and do the compiling there:

content/donate/_index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ _This might change in future as the project grows along with its potential costs
2929

3030
All these said, if you would like to financially contribute to the Flameshot project, we suggest you to use code bounty platform to put bounty on the issues (bugs or feature requests). This way your money and contribution goes directly towards improving Flameshot as you see it fit and would immediately benefit you and other users. This is also a good way to get the features implemented that you want, or get the bugs that annoys you fixed. The beautiful part of this approach is that multiple people can put bounty on the same issue which would increase the chance of getting it addressed by one of the developers in that platform.
3131

32-
At the moment are looking for a platform that does code bounty. If you know any platform suitable for this, please send us an email (info@ this domain) or open an issue on [this Github repo](https://github.com/flameshot-org/flameshot-org.github.io/issues/) or the [main repo](https://github.com/flameshot-org/flameshot/issues/).
32+
At the moment are looking for a platform that does code bounty. If you know any platform suitable for this, please send us an email (info@ this domain) or open an issue on [this GitHub repo](https://github.com/flameshot-org/flameshot-org.github.io/issues/) or the [main repo](https://github.com/flameshot-org/flameshot/issues/).
3333

3434
## Other form of donation
3535

0 commit comments

Comments
 (0)