Few edits

Author: tristanlabelle

docs/weblate.md

@@ -1,4 +1,6 @@
-# Weblate aka translation platform dev guide
+# Weblate dev guide
+
+Weblate is our translation platform which we self-host at https://translate.couchershq.org. It provides a UI for translators to consume our `locales/en.json` files and produce `locales/<not-en>.json` files for every locale we support.
 
 Weblate maintains a clone of the `git` repo. It appends commits with translation changes to its `develop` branch, and periodically opens pull requests to merge its `develop` branch into GitHub's. Sometimes conflicts can happen where this merge operation fails, at which point Weblate locks up until we resolve it.
 
@@ -14,7 +16,7 @@ git fetch weblate develop
 
 ## Avoiding conflicts
 
-- ✅ DO: Always merge Weblate PRs using the `merge` strategy. To make this easier, [.github/weblate-automerge.yml] will mark new Weblate PRs as auto-merging with the `merge` strategy.
+- ✅ DO: Always merge Weblate PRs using the `merge` strategy. To make this easier, the [weblate-automerge.yml](.github/weblate-automerge.yml) GitHub workflow will mark new Weblate PRs as auto-merging with the `merge` strategy.
   - ❌ DO NOT: Merge them using the `squash` strategy.
 - ✅ DO: Whenever possible, only modify `en.json` files in GitHub, and only modify translation files via Weblate.
   - ❌ AVOID: Modifying translation files in GitHub.
@@ -37,11 +39,11 @@ If you're confident that your string's translations and its viscinity are not be
 1. Refactor the string keys, open a PR and merge it.
 1. Unlock the Weblate component.
 
-## Why Weblate conflicts occur
+## Why conflicts occur
 
 Weblate conflicts occur when it fails to reconciliate GitHub's `develop` branch with its own `develop`, meaning that a translation file was modified in GitHub and differently in Weblate. Surprisingly, conflicts are also likely when merging Weblate PRs using the `squash` strategy, since Weblate's won't find its commits in upstream, and its individual commits might conflict with the final squashed commit in GitHub, even if they lead to the same file state. For this reason, Webl
 
-## Resolving Weblate conflicts
+## Resolving conflicts
 
 The goal of conflict resolution is to allow Weblate to reconciliate its queued commits with what's already in GitHub. Weblate gives a few tools to modify its `develop` branch, but those are fraught (big scary red buttons), so the better approach is to merge Weblate's queued commits into GitHub, after which it will automatically clear its queue. Follow the steps below, and make sure to merge your PR with the `merge` strategy!