Congegni/sintonia
7
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

docs: fix vale linting errors

Browse source 
- are not > aren't
- auto-_ > auto _
- avoid backend
- cannot > can't
- do not > don't
- does not > doesn't
- ignore emoji code
- has not > hasn't
- ignore Microsoft.GeneralURL
- is not > isn't
- it is > it's
- no exclamation point
- put code inside code blocks
- put commit sha inside code blocks
- put exception message in code blocks
- remove slang
- should not > shouldn't
- they are > they're
- we are > we're
- will not > won't
This commit is contained in:
jo 2022-09-24 17:40:05 +02:00 • committed by Kyle Robbertze
parent 722a683896
commit 50809a933c
42 changed files with 174 additions and 160 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/developer-manual/design/architecture.md
View file

@ -67,13 +67,13 @@ The LibreTime architecture is split into 2 main monolithic blocks `Create the sc
:::note
A microservice architecture was rejected as it will not fix or improve any aspect of LibreTime.
A microservice architecture was rejected as it won't fix or improve any aspect of LibreTime.
:::
:::warning
This document tries to focus on creating and playing a schedule, it does not consider features such as monitoring, logging or archiving.
This document tries to focus on creating and playing a schedule, it doesn't consider features such as monitoring, logging or archiving.
:::
@ -90,7 +90,7 @@ The web API, the worker and the message API rely on the [Django framework](https
### Play the schedule
Since the `Play the schedule` has its own requirements in terms of logic and uptime, it is handled separately from the `Create the schedule` block. This block needs to be able to be duplicated in a high availability context.
Since the `Play the schedule` has its own requirements in terms of logic and uptime, it's handled separately from the `Create the schedule` block. This block needs to be able to be duplicated in a high availability context.
This block contains the following components:
@ -101,7 +101,7 @@ This block contains the following components:
### One setup per radio station
LibreTime is not meant to be used in a multi-tenant architecture, and an entire LibreTime installation should be dedicated to a single radio station. Previous SAAS or multi-tenant features from Airtime should be deprecated or removed.
LibreTime isn't meant to be used in a multi-tenant architecture, and an entire LibreTime installation should be dedicated to a single radio station. Previous SAAS or multi-tenant features from Airtime should be deprecated or removed.
### Separation of concerns

2
docs/developer-manual/design/database-migrations.md
View file

@ -8,7 +8,7 @@ Since LibreTime forked, the `schema_version` in the `schema.sql` was locked on `
:::
Django does not maintain a `schema.sql` file, it applies every migrations until it reaches the targeted schema represented by the code. The legacy `schema_version` has to be tracked until we remove the Propel schema generation and let Django handle all the schema migrations. Until then Propel generate the schema and Django handle migrations from already installed databases.
Django doesn't maintain a `schema.sql` file, it applies every migrations until it reaches the targeted schema represented by the code. The legacy `schema_version` has to be tracked until we remove the Propel schema generation and let Django handle all the schema migrations. Until then Propel generate the schema and Django handle migrations from already installed databases.
:::info