From 52134b3617442ddedd8dc1c08192b531383365f2 Mon Sep 17 00:00:00 2001 From: omahs <73983677+omahs@users.noreply.github.com> Date: Tue, 5 Sep 2023 05:23:21 +0200 Subject: [PATCH] fix(docs): typos (#10143) --- docs/Build LogSeq Desktop for windows on Ubuntu.md | 2 +- docs/accessibility.md | 6 +++--- docs/contributing-to-translations.md | 6 +++--- src/resources/tutorials/tutorial-fr.md | 2 +- 4 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/Build LogSeq Desktop for windows on Ubuntu.md b/docs/Build LogSeq Desktop for windows on Ubuntu.md index 8e504839976..3b24e9f738f 100644 --- a/docs/Build LogSeq Desktop for windows on Ubuntu.md +++ b/docs/Build LogSeq Desktop for windows on Ubuntu.md @@ -1,7 +1,7 @@ # Building Logseq Desktop app for Windows on Ubuntu ## Intro My Logseq dev machine is on Ubuntu 18.x and my production machine is running Windows 10, I needed a way to compile the Logseq desktop APP for Windows. -I tired & failed to make the "build" run on my windows machine but I did, however, succeed in letting my Ubuntu machine make Windows x64 files +I tried & failed to make the "build" run on my windows machine but I did, however, succeed in letting my Ubuntu machine make Windows x64 files ## Pre-requisites These are the steps I took to make it work on my Ubuntu machine, sharing them hoping it helps someone else. I assume you have all the basic pre-requisites for Logseq, if not you can find them at https://github.com/logseq/logseq#1-requirements 1. clone Logseq repo if you haven't already diff --git a/docs/accessibility.md b/docs/accessibility.md index 11cc086ec73..31d52aaa071 100644 --- a/docs/accessibility.md +++ b/docs/accessibility.md @@ -1,4 +1,4 @@ -- Accessibility is a vague term, which is why it is usually misunderstood. It is not just about people with with specific disabilities. You can read more about [what is accessibility](https://developer.mozilla.org/en-US/docs/Learn/Accessibility/What_is_accessibility#so_what_is_accessibility) and [diverse abilities and barriers](https://www.w3.org/WAI/people-use-web/abilities-barriers/). +- Accessibility is a vague term, which is why it is usually misunderstood. It is not just about people with specific disabilities. You can read more about [what is accessibility](https://developer.mozilla.org/en-US/docs/Learn/Accessibility/What_is_accessibility#so_what_is_accessibility) and [diverse abilities and barriers](https://www.w3.org/WAI/people-use-web/abilities-barriers/). - ## Web Content Accessibility Guidelines - [WCAG](https://www.w3.org/WAI/standards-guidelines/wcag/) (Web Content Accessibility Guidelines) is the international standard for web content accessibility, developed by [W3C](https://www.w3.org/). Logseq is a web application, so conforming with WCAG should be our first priority. In general, there is no simple way to determine if a website is accessible or not, but WCAG can help us make the tool usable by as many people as possible. - ## Levels of conformance @@ -6,7 +6,7 @@ - Level **A** is the minimum level. - Level **AA** includes all Level A and AA requirements. - Level **AAA** includes all Level A, AA, and AAA requirements. - - Many organizations strive to meet Level AA. The reason behind this decision, is that in some cases AAA standard is too strict. That does't mean that triple-A issues should be disregarded. On the contrary, all of them should be handled if possible. + - Many organizations strive to meet Level AA. The reason behind this decision, is that in some cases AAA standard is too strict. That doesn't mean that triple-A issues should be disregarded. On the contrary, all of them should be handled if possible. - We can also provide alternative options in order to conform with AAA standards. For instance, our default themes can aim for AA, but we can provide a high-contrast theme that aims for AAA. Providing [alternative versions](https://www.w3.org/WAI/GL/2007/05/alternate-versions.html) with different levels of conformance is permitted according to WCAG, if there is an accessible way to reach those alternatives. - ## Simple development guidelines - Use semantically correct markup whenever possible. Every time you are about to decide which html tag you are going to use, choose the one that behaves the way you want it. For example, let's say you want to create an element that looks like plain text, but triggers an action on click. Usually, the best approach would be to create a `