Replace Riot with Element in docs and comments

This only covers the simple cases of references to issues and repos. More
complex areas, such as deployment scripts, will be handled separately.

Part of https://github.com/vector-im/element-web/issues/14864

docs/ciderEditor.md

@@ -1,6 +1,6 @@
 # The CIDER (Contenteditable-Input-Diff-Error-Reconcile) editor
 
-The CIDER editor is a custom editor written for Riot.
+The CIDER editor is a custom editor written for Element.
 Most of the code can be found in the `/editor/` directory of the `matrix-react-sdk` project.
 It is used to power the composer main composer (both to send and edit messages), and might be used for other usecases where autocomplete is desired (invite box, ...).
 

docs/jitsi.md

@@ -25,7 +25,7 @@ which takes several parameters:
   be null.
 
 The react-sdk will assume that `jitsi.html` is at the path of wherever it is currently
-being served. For example, `https://riot.im/develop/jitsi.html` or `vector://webapp/jitsi.html`.
+being served. For example, `https://develop.element.io/jitsi.html` or `vector://webapp/jitsi.html`.
 
 The `jitsi.html` wrapper can use the react-sdk's `WidgetApi` to communicate, making
 it easier to actually implement the feature.

docs/room-list-store.md

@@ -55,7 +55,7 @@ timestamp contained within the event (generated server-side by the sender's serv
 
 This is the easiest of the algorithms to understand because it does essentially nothing. It imposes no
 behavioural changes over the tag sorting algorithm and is by far the simplest way to order a room list.
-Historically, it's been the only option in Riot and extremely common in most chat applications due to
+Historically, it's been the only option in Element and extremely common in most chat applications due to
 its relative deterministic behaviour.
 
 ### List ordering algorithm: Importance

docs/scrolling.md

@@ -13,7 +13,7 @@ ScrollPanel supports a mode to prevent it shrinking. This is used to prevent a j
 
 BACAT scrolling implements a different way of restoring the scroll position in the timeline while tiles out of view are changing height or tiles are being added or removed. It was added in https://github.com/matrix-org/matrix-react-sdk/pull/2842.
 
-The motivation for the changes is having noticed that setting scrollTop while scrolling tends to not work well, with it interrupting ongoing scrolling and also querying scrollTop reporting outdated values and consecutive scroll adjustments cancelling each out previous ones. This seems to be worse on macOS than other platforms, presumably because of a higher resolution in scroll events there. Also see https://github.com/vector-im/riot-web/issues/528. The BACAT approach allows to only have to change the scroll offset when adding or removing tiles.
+The motivation for the changes is having noticed that setting scrollTop while scrolling tends to not work well, with it interrupting ongoing scrolling and also querying scrollTop reporting outdated values and consecutive scroll adjustments cancelling each out previous ones. This seems to be worse on macOS than other platforms, presumably because of a higher resolution in scroll events there. Also see https://github.com/vector-im/element-web/issues/528. The BACAT approach allows to only have to change the scroll offset when adding or removing tiles.
 
 The approach taken instead is to vertically align the timeline tiles to the bottom of the scroll container (using flexbox) and give the timeline inside the scroll container an explicit height, initially set to a multiple of the PAGE_SIZE (400px at time of writing) as needed by the content. When scrolled up, we can compensate for anything that grew below the viewport by changing the height of the timeline to maintain what's currently visible in the viewport without adjusting the scrollTop and hence without jumping.
 

docs/usercontent.md

@@ -5,9 +5,9 @@ letting the browser and user interact with the resulting data may be dangerous,
 previously `usercontent.riot.im` was used to act as a sandbox on a different origin to close the attack surface,
 it is now possible to do by using a combination of a sandboxed iframe and some code written into the app which consumes this SDK.
 
-Usercontent is an iframe sandbox target for allowing a user to safely download a decrypted attachment from a sandboxed origin where it cannot be used to XSS your riot session out from under you.
+Usercontent is an iframe sandbox target for allowing a user to safely download a decrypted attachment from a sandboxed origin where it cannot be used to XSS your Element session out from under you.
 
-Its function is to create an Object URL for the user/browser to use but bound to an origin different to that of the riot instance to protect against XSS.
+Its function is to create an Object URL for the user/browser to use but bound to an origin different to that of the Element instance to protect against XSS.
 
 It exposes a function over a postMessage API, when sent an object with the matching fields to render a download link with the Object URL:
 
@@ -24,4 +24,4 @@ It exposes a function over a postMessage API, when sent an object with the match
 
 If only imgSrc, imgStyle and style are passed then just update the existing link without overwriting other things about it.
 
-It is expected that this target be available at `usercontent/` relative to the root of the app, this can be seen in riot-web's webpack config.
+It is expected that this target be available at `usercontent/` relative to the root of the app, this can be seen in element-web's webpack config.