From 25d94e8c140e8a7d402e89e369fd9566ff818353 Mon Sep 17 00:00:00 2001 From: N3WK1D Date: Sun, 23 Jul 2023 11:04:31 -0600 Subject: [PATCH 1/5] Fixed grammar and typos. --- FAQ.md | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/FAQ.md b/FAQ.md index 5545496918..056e832205 100644 --- a/FAQ.md +++ b/FAQ.md @@ -47,7 +47,7 @@ Some x86_64 hosts running older versions of the Docker engine are not compatible ## My host is incompatible with images based on rdesktop {#rdesktop} -Some x86_64 hosts have issues running rdesktop based images even with the latest docker version due to syscalls that are unknown to docker. +Some x86_64 hosts have issues running rdesktop based images even with the latest Docker version due to syscalls that are unknown to Docker. - Symptoms @@ -74,7 +74,7 @@ Some x86_64 hosts have issues running rdesktop based images even with the latest This only affects 32 bit installs of distros based on Debian Buster. -This is due to a bug in the libseccomp2 library (dependency of Docker itself), which is fixed. However it's not pushed to all the repositories. +This is due to a bug in the libseccomp2 library (dependency of Docker itself), which is fixed. However, it's not pushed to all the repositories. [A GitHub issue tracking this](https://github.com/moby/moby/issues/40734) @@ -131,11 +131,11 @@ You have a few options as noted below. Options 1 is short-term, while option 2 i ## What is lscr.io {#lscr} -LSCR is a vanity url for our images, this is provided to us in collaboration with [scarf.sh](https://about.scarf.sh/). It is not a dedicated docker registry, rather a redrection service. As of writing it redirects to GitHub Container Registry(ghcr.io). +LSCR is a vanity url for our images, this is provided to us in collaboration with [scarf.sh](https://about.scarf.sh/). It is not a dedicated docker registry, rather a redirection service. As of writing it redirects to GitHub Container Registry (ghcr.io). -Aside from giving us the ability to redirect to another backend, if nesseceary, it also exposes telemetry about pulls, historically only available to the backend provider. We base some decisions on this data, as it gives us a somewhat realistic useage overview (realative to just looking at pulls on DockerHub). +Aside from giving us the ability to redirect to another backend, if necessary, it also exposes telemetry about pulls, historically only available to the backend provider. We base some decisions on this data, as it gives us a somewhat realistic usage overview (relative to just looking at pulls on DockerHub). -We have some blogpost related to how we utilize Scarf: +We have some blog posts related to how we utilize Scarf: - [End of an Arch](https://www.linuxserver.io/blog/end-of-an-arch) - [Unravelling Some Stats](https://www.linuxserver.io/blog/unravelling-some-stats) @@ -149,13 +149,13 @@ If you want to help us in getting a better overview of how people use our contai Alternatively, you can use Docker Hub or GHCR directly to pull your images, although be aware that all public registries gather user metrics, so this doesn't provide you with any real benefit in that area. -If Scarf is on the blocklist, you will get a error message like this when trying to pull a image: +If Scarf is on the blocklist, you will get an error message like this when trying to pull an image: ``` Error response from daemon: Get "https://lscr.io/v2/": dial tcp: lookup lscr.io: no such host ``` -This is however a generic message, to rule out a service-interuption, you should also see if you can resolve the backend provider. +This is, however, a generic message. To rule out a service-interruption, you should also see if you can resolve the backend provider. Using dig: @@ -171,15 +171,15 @@ nslookup ghcr.io nslookup lscr.io ``` -If you only got a response from ghcr, chances are that Scarf is on the blocklist +If you only got a response from ghcr, chances are that Scarf is on the blocklist. -## I want to reverse proxy a application which defaults to https with a selfsigned certificate {#strict-proxy} +## I want to reverse proxy an application which defaults to https with a self-signed certificate {#strict-proxy} ### Traefik {#strict-proxy-traefik} -In this example we will configure a serverTransport rule we can apply to a service, as well as telling Traefik to use https on the backend for the service. +In this example, we will configure a serverTransport rule we can apply to a service, as well as telling Traefik to use https on the backend for the service. -Create a [ServerTransport](https://doc.traefik.io/traefik/routing/services/#serverstransport_1) in your dynamic Traefik configuration, we are calling ours `ignorecert`. +Create a [ServerTransport](https://doc.traefik.io/traefik/routing/services/#serverstransport_1) in your dynamic Traefik configuration; we are calling ours `ignorecert`. ```yml http: From 746028d15334a8a7d1d07b21c84e3e257d49a7b3 Mon Sep 17 00:00:00 2001 From: N3WK1D Date: Sun, 23 Jul 2023 11:17:39 -0600 Subject: [PATCH 2/5] Fixed grammar and typos. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index c9dc6d0ee5..04e49a2c67 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ # Introduction -Welcome to the home of the LinuxServer.io documentation! It is our goal to ensure that all of our images are properly documented with all of the relevant information in order to help our users get started. As well as individual set up guides for each of our images, there is also general information pertaining to the running of Docker containers, and best practices. +Welcome to the home of the LinuxServer.io documentation! It is our goal to ensure that all of our images are properly documented with all of the relevant information, in order to help our users get started. In addition to individual set up guides for each image, there is also general information, and best practices, pertaining to running Docker containers. ## Want to get hold of the team? From 12f29dba77fa4104aad1858ead210f956fe47494 Mon Sep 17 00:00:00 2001 From: N3WK1D Date: Sun, 23 Jul 2023 11:30:24 -0600 Subject: [PATCH 3/5] Fixed grammar and typos. --- finances.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/finances.md b/finances.md index 66352d6749..11ca0b519c 100644 --- a/finances.md +++ b/finances.md @@ -20,16 +20,16 @@ We will at all times attempt to keep a surplus of $6,000 in the bank account, or ## Votes -In order for money to be approved for a project, the requesting member must go through every effort to bring to vote a fully formed idea that is ready to be actioned. This means that all the legwork is done before bringing an idea to vote, or at least as much as is reasonably possible. A vote will last for 3 days in order to give all team members the opportunity to participate without unnecessarily causing delays. A generasl consensus will need to be reached in order for it to proceed. +In order for money to be approved for a project, the requesting member must go through every effort to bring to vote a fully formed idea that is ready to be actioned. This means that all the legwork is done before bringing an idea to vote, or at least as much as is reasonably possible. A vote will last for 3 days in order to give all team members the opportunity to participate without unnecessarily causing delays. A general consensus will need to be reached in order for it to proceed. ## Acceptable uses of money * Hardware/Software needed to help the group reach a specific goal -* Stationary + Related items for possible Conventions -* Convention Fees (Both Attendence and Travel) +* Stationary + related items for possible conventions +* Convention fees (Both Attendence and Travel) * Hosting services (Included domain purchases) -* Good will gestures (Example: For users outside the group that have provided help when asked) -* Food/Drink for LinuxServer.io focused sprints. +* Good will gestures (Example: For users outside the group that have provided help when asked.) +* Food/Drink for LinuxServer.io focused sprints * Donations to upstream projects ## Links From c2628d8cc9bfe92d4dd792aebc522c59ff80e23f Mon Sep 17 00:00:00 2001 From: N3WK1D Date: Sun, 23 Jul 2023 11:35:59 -0600 Subject: [PATCH 4/5] Fixed grammar and typos. --- FAQ.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/FAQ.md b/FAQ.md index 056e832205..87e84677c0 100644 --- a/FAQ.md +++ b/FAQ.md @@ -1,6 +1,6 @@ # FAQ -Here will some Frequently Asked Questions reside +Here resides some Frequently Asked Questions. ## My host is incompatible with images based on Ubuntu Jammy {#jammy} From 74efe25dfc715ab069d1d739e091c46d4f6b3ca6 Mon Sep 17 00:00:00 2001 From: N3WK1D Date: Sun, 23 Jul 2023 11:37:37 -0600 Subject: [PATCH 5/5] Fixed grammar and typos. --- FAQ.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/FAQ.md b/FAQ.md index 87e84677c0..a073c8fc9c 100644 --- a/FAQ.md +++ b/FAQ.md @@ -30,7 +30,7 @@ Some x86_64 hosts running older versions of the Docker engine are not compatible - Option 1 (Long-Term Fix) - Upgrade your Docker engine install to at least version `20.10.10`. [Refer to the official Docker docs for installation/update details.](https://docs.docker.com/engine/install) + Upgrade your Docker engine to at least version `20.10.10`. [Refer to the official Docker docs for installation/update details.](https://docs.docker.com/engine/install) - Option 2 (Short-Term Fix)