Update docs to align better with community and our conventions

Author: grilme99

docs/align-files-guide.md

@@ -1,14 +1,15 @@
 # Aligning files guide
 
-We are aligning files by going through them module by module. We keep track of them in a [Adapt roact-alignment implementation](https://github.com/Roblox/roact-alignment/milestone/1) milestone.
+We are aligning files by going through them module by module.
 
 ## Prerequisites
 
 In this guide we assume that you have the following project cloned inside of the common directory:
+
 * js-to-lua [repo link](https://github.com/roblox/js-to-lua)
   * checkout `main` branch
-* roact-alignment [repo link](https://github.com/roblox/roact-alignment)
-  * your working branch on top of `master` branch
+* react-lua [repo link](https://github.com/jsdotlua/react-lua)
+  * your working branch on top of `main` branch
 * react [repo link](https://github.com/facebook/react)
   * checkout `v17.0.2` tag
 
@@ -25,7 +26,7 @@ Depending on the size of the module and/or your preference you can either align
 ```shell
 dist/apps/convert-js-to-lua/index.js \
   --input ../react/packages/react-devtools-shared/src/**/*.js \
-  --output ../roact-alignment/modules/ \
+  --output ../react-lua/modules/ \
   --rootDir ../react/packages \
   --plugin=knownImports --plugin=jestGlobals \
   --babelTransformConfig babel-flow-transform-react.config.json \
@@ -37,7 +38,7 @@ This will run the conversion on all the files in the `react-devtools-shared` whi
 ```shell
 dist/apps/convert-js-to-lua/index.js \
   --input ../react/packages/react-devtools-shared/src/<path_to_a_js_file> \
-  --output ../roact-alignment/modules/ \
+  --output ../react-lua/modules/ \
   --rootDir ../react/packages \
   --plugin=knownImports --plugin=jestGlobals \
   --babelTransformConfig babel-flow-transform-react.config.json \
@@ -46,17 +47,17 @@ dist/apps/convert-js-to-lua/index.js \
 
 eg.
 
-```
+```shell
 dist/apps/convert-js-to-lua/index.js \
   --input ../react/packages/react-devtools-shared/src/utils.js \
-  --output ../roact-alignment/modules/ \
+  --output ../react-lua/modules/ \
   --rootDir ../react/packages \
   --plugin=knownImports --plugin=jestGlobals \
   --babelTransformConfig babel-flow-transform-react.config.json \
   --babelConfig babel-flow.config.json
 ```
 
-After we run the automatic conversion the file will contain a lot of changes. Please additionally run `stylua module` in the roact-alignment directory to make sure all the files are converted according to the StyLua configuration.
+After we run the automatic conversion the file will contain a lot of changes. Please additionally run `stylua module` in the react-lua directory to make sure all the files are converted according to the StyLua configuration.
 
 Now our job is to capture the deviations that the original code has made and mark them with appropriate `ROBLOX deviation START` / `ROBLOX deviation END` comments.
 
@@ -81,7 +82,7 @@ As for the actual deviations that need to be marked let's look at the following
 ![Bridge shutdown method's diff before marking a deviation](diff-bridge-shutdown-method-before.png)
 ![Bridge shutdown method's diff after marking a deviation](diff-bridge-shutdown-method-after.png)
 
-In order to make that process a little bit easier we've created a set of VSCode snippets that you can use - [link](#snippets) to snippets section. 
+In order to make that process a little bit easier we've created a set of VSCode snippets that you can use - [link](#snippets) to snippets section.
 
 ## Snippets
 
@@ -95,6 +96,7 @@ In order to use the snippets you should configure a hot key (keyboard shortcut)
 * `deviation-start` and `deviation-end` - will only insert a proper deviation start/end comment. We use those to avoid typos.
 
 There are couple more utility snippets for special cases that were occurring more often:
+
 * `deviation-block-type` - it will wrap a block with deviation comments, comment out the block and insert a duplicate but change `local` for `type`. It's useful when js-to-lua imported locals from a module when it should actually import types
 * `deviation-line` and `deviation-line-skipped` are similar to their block equivalents but will use the current line instead of selected block of code
 

docs/api-reference/react-roblox.md

@@ -10,50 +10,58 @@ Notable absences are:
 * `unmountComponentAtNode` - Use the `unmount` method on the root object returned from `createRoot` instead
 * `findDOMNode` - Use [refs](https://reactjs.org/docs/refs-and-the-dom.html) instead
 
-## ReactRoblox.createRoot
+## `ReactRoblox.createRoot`
+
 Adopted as part of the Concurrent Mode API. Refer to [`ReactDOM.createRoot` documentation](https://reactjs.org/docs/concurrent-mode-reference.html#createroot).
 
-## ReactRoblox.createBlockingRoot
+## `ReactRoblox.createBlockingRoot`
+
 Adopted as part of the Concurrent Mode API. "Blocking" roots represent a transitional step between synchronous rendering and full concurrent rendering. Refer to [`ReactDOM.createBlockingRoot` documentation](https://reactjs.org/docs/concurrent-mode-adoption.html#migration-step-blocking-mode).
 
-## ReactRoblox.createLegacyRoot
+## `ReactRoblox.createLegacyRoot`
+
 Adopted as part of the Concurrent Mode API. "Legacy" roots are essentially equivalent to pre-concurrent React behavior. Refer to [`ReactDOM.createLegacyRoot` documentation](https://reactjs.org/docs/concurrent-mode-adoption.html#migration-step-blocking-mode).
 
 ### Deviations
+
 React documentation provides [a handy chart](https://reactjs.org/docs/concurrent-mode-adoption.html#feature-comparison) that explains the feature differences between the roots. This table lists three deprecated features under legacy roots only:
 
 * [String Refs](https://reactjs.org/docs/refs-and-the-dom.html#legacy-api-string-refs)
 * [Legacy Context](https://reactjs.org/docs/legacy-context.html)
 * [findDOMNode](https://reactjs.org/docs/strict-mode.html#warning-about-deprecated-finddomnode-usage)
 
-**These features were never implemented in legacy Roact, and have not been ported.** Instead, creating a Legacy Mode root simply tells Roact to render synchronously. This behavior is most similar to legacy Roact or pre-Concurrent-Mode React JS.
+**These features were never implemented in legacy Roact, and have not been ported.** Instead, creating a Legacy Mode root simply tells React Lua to render synchronously. This behavior is most similar to legacy Roact or pre-Concurrent-Mode React JS.
 
 Generally speaking, `ReactRoblox.createRoot` should be used for all new work, while the Blocking and Legacy versions can be used for upgrading existing Roact logic in the event that it does not yet meet the requirements for Concurrent Mode.
 
-## ReactRoblox.createPortal
+## `ReactRoblox.createPortal`
+
 Refer to [`ReactDOM.createPortal` documentation](https://reactjs.org/docs/portals.html).
 
 <!-- Testing/globals only -->
-## ReactRoblox.act
-Used for testing code with scheduling logic mocked. This ensures that tests behave consistently and don't batch work unpredictably across frames. `act` executes a function and then plays forward the mock scheduler after it's done, and should be used to wrap any interactions that trigger updates to a roact UI.
+## `ReactRoblox.act`
 
-More info on using `act` can be found [in the migration guide](../migrating-from-1x/adopt-new-features.md#reactrobloxact).
+Used for testing code with scheduling logic mocked. This ensures that tests behave consistently and don't batch work unpredictably across frames. `act` executes a function and then plays forward the mock scheduler after it's done, and should be used to wrap any interactions that trigger updates to a React UI.
+
+More info on using `act` can be found [in the migration guide](../migrating-from-legacy/adopt-new-features.md#reactrobloxact).
 
 Refer to [ReactDOM's `act` testing documentation](https://reactjs.org/docs/test-utils.html#act) for more high-level guidance.
 
 ### Deviations
+
 In production, `ReactRoblox.act` will not be available. Set the global value `_G.__ROACT_17_INLINE_ACT__` to `true` in order to enable this behavior in tests.
 
 !!! info
-	This behavior is still a work in progress, and there may be changes to how Roact detects whether or not it should provide the `act` function. For now, use the global `__ROACT_17_INLINE_ACT__` to enable it for tests.
+	This behavior is still a work in progress, and there may be changes to how React Lua detects whether or not it should provide the `act` function. For now, use the global `__ROACT_17_INLINE_ACT__` to enable it for tests.
+
+## `ReactRoblox.Event`
 
-## ReactRoblox.Event
 *Roact-only*
 
 Re-exports [`React.Event`](react.md#reactevent). This is only exposed for backwards compatibility; please prefer to use `React.Event`.
 
-## ReactRoblox.Change
+## `ReactRoblox.Change`
+
 *Roact-only*
 
 Re-exports [`React.Change`](react.md#reactchange). This is only exposed for backwards compatibility; please prefer to use `React.Change`.
-