remove accessibility, upstream, and schema links (#102)

custom_conf.py

@@ -133,15 +133,12 @@
     'Debugging#Profiling%20page%20requests',  # needs update
     'Debugging#Special%20URLs',  # needs update
     'JavascriptUnitTesting/MockIo',  # needs update
-    'PolicyAndProcess/Accessibility',  # needs update
-    'Translations/Specs/UpstreamImportIntoUbuntu/FixingIsImported/setCurrentTranslation',  # needs update
     'https://git.launchpad.net/launchpad-mojo-specs/tree/mojo-lp-git/services',  # private
     'https://wiki.canonical.com/InformationInfrastructure/OSA/LaunchpadProductionStatus',  # private
     'https://wiki.canonical.com/Launchpad/PolicyandProcess/ProductionChange',  # private
     'https://wiki.canonical.com/Launchpad/PolicyandProcess/ProductionChangeApprovalPolicy',  # private
     'https://deployable.ols.canonical.com/project/launchpad-db',  # private
     'irc.libera.chat',  # this is not an HTTP link
-    'attachment:TranslationsSchema.dia',  # needs update
     r'https://github\.com/canonical/fetch-service*',  # private
     r'https://github\.com/canonical/fetch-operator*',  # private
     'https://git.launchpad.net/charm-launchpad-buildd-image-modifier/tree/files/scripts/setup-ppa-buildd',  # private

explanation/engineering-overview-translations.rst

@@ -315,9 +315,6 @@ Message sharing
 Objects and schema
 ------------------
 
-See my horrible `schema overview <attachment:TranslationsSchema.dia>`__
-(dia format).
-
 In a nutshell:
 
 -  A \`POTemplate\` lives in either a \`ProductSeries\` or a
@@ -370,9 +367,7 @@ A translation message can be in one of three sharing states:
 3. **Tracking.** The translation is not only shared on one translation
    side, but between both translation sides.
 
-We have a `design
-document <Translations/Specs/UpstreamImportIntoUbuntu/FixingIsImported/setCurrentTranslation>`__
-that specifies how messages in these states respond to changes. We try
+We have a design document that specifies how messages in these states respond to changes. We try
 to make it easy to move a translation down this list (towards tracking)
 and hard to move up the list (towards diverged).
 

how-to/triage-bugs.rst

@@ -16,8 +16,8 @@ We want:
    are dependencies of other critical bugs.
 -  The *High* bugs list to be our main set of top priorities. Some
    specific sorts of bugs we always treat as high. Right now: OOPSes,
-   timeouts, A and AA `treat accessibility
-   bugs <PolicyAndProcess/Accessibility>`__.
+   timeouts, A and AA treat accessibility
+   bugs.
 
 We would prefer to be able to treat OOPSes and timeouts as critical, as it
 was the case until 2020, but having a practically-usable Critical queue
@@ -95,17 +95,17 @@ High
 These are bugs that will be our main focus in normal operation, timeouts
 (tagged "timeout"), OOPSes (thanks to our `zero OOPS
 policy <https://dev.launchpad.net/PolicyAndProcess/ZeroOOPSPolicy>`__,
-and tagged "oops"), and A and AA conformance `accessibility
-bugs <PolicyAndProcess/Accessibility>`__.
+and tagged "oops"), and A and AA conformance accessibility
+bugs.
 
 Low
 ~~~
 
 We mark as *Low* any bug that we recognise as legitimate but that is
 **not** a priority for Canonical staff to fix. This is not the same as
 planning not to fix the bug; it means that we don't know when we will
-fix it, if at all. This includes AAA conformance `accessibility
-bugs <PolicyAndProcess/Accessibility>`__.
+fix it, if at all. This includes AAA conformance accessibility
+bugs.
 
 Others
 ~~~~~~