Update links to old repo

Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>

apps/desktop/docs/config.md

@@ -4,12 +4,12 @@ All Element Web options documented [here](https://github.com/vector-im/element-w
 
 ---
 
-The app contains a configuration file specified at build time using [these instructions](https://github.com/vector-im/element-desktop/#config).
-This config can be overwritten by the end using by creating a `config.json` file at the paths described [here](https://github.com/vector-im/element-desktop/#user-specified-configjson).
+The app contains a configuration file specified at build time using [these instructions](https://github.com/element-hq/element-web/blob/develop/apps/desktop/README.md#config).
+This config can be overwritten by the end using by creating a `config.json` file at the paths described [here](https://github.com/element-hq/element-web/blob/develop/apps/desktop/README.md#user-specified-configjson).
 
 After changing the config, the app will need to be exited fully (including via the task tray) and re-started.
 
 ---
 
-1. `update_base_url`: Specifies the URL of the update server, see [document](https://github.com/vector-im/element-desktop/blob/develop/docs/updates.md).
+1. `update_base_url`: Specifies the URL of the update server, see [document](https://github.com/element-hq/element-web/blob/develop/apps/desktop/docs/updates.md).
 2. `web_base_url`: Specifies the Element Web URL when performing actions such as popout widget. Defaults to `https://app.element.io/`.

apps/desktop/docs/gdb.md

@@ -13,7 +13,7 @@ you will need debug symbols.
 2. Figure out which version of Electron your Element-Desktop is based on. The
    best way to do this is to figure out the version of Element-Desktop, then
    look at
-   [`package.json`](https://github.com/element-hq/element-desktop/blob/develop/package.json)
+   [`package.json`](https://github.com/element-hq/element-web/blob/develop/apps/desktop/package.json)
    for the corresponding version. There will be an entry within `dependencies` of
    `electron`: the value will tell you the version of Electron that was used for that version of Element-Desktop.
 

apps/desktop/docs/native-node-modules.md

@@ -33,13 +33,13 @@ pnpm link docker/node_modules/matrix-seshat
 
 ... and build the app with `pnpm build` or run it with `pnpm start`.
 
-(See also https://github.com/element-hq/element-desktop#docker.)
+(See also https://github.com/element-hq/element-web/blob/develop/apps/desktop/README.md#docker.)
 
 ## Building
 
 Install the pre-requisites for your system:
 
-- [Windows pre-requisites](https://github.com/vector-im/element-desktop/blob/develop/docs/windows-requirements.md)
+- [Windows pre-requisites](https://github.com/element-hq/element-web/blob/develop/apps/desktop/docs/windows-requirements.md)
 - Linux: TODO. Using the docker environment as above is recommended.
 - OS X: TODO
 

apps/desktop/docs/packaging.md

@@ -13,16 +13,7 @@ Simply go to https://github.com/vector-im/element-desktop/actions/workflows/buil
 
 ## Packaging releases
 
-**Don't do this for RCs! We don't build Element Desktop for RCs.**
-
-For releasing Element Desktop, we assume the following prerequisites:
-
-- a tag of `element-desktop` repo with the Element Desktop version to be released set in `package.json`.
-- an Element Web tarball published to GitHub with a matching version number.
-
-**Both of these are done automatically when you run the release automation.**
-
-The packaging is kicked off automagically for you when a Github Release for Element Desktop is published.
+The packaging is kicked off automagically for you when a Github Release for Element Web is published.
 
 ### More detail on the github actions