Improve clarity in RNW 0.80 docs and migration guide (#1093)

# 📝 Improve React Native Windows v0.80 Documentation

This PR enhances the user experience and clarity of React Native Windows
v0.80 documentation based on community feedback and PR review comments.

## 🎯 Key Improvements

### Getting Started Guide
- ✅ **Added prerequisites callout** to prevent setup issues
- ✅ **Enhanced command explanations** - added context for why each step
is needed
- ✅ **Separate explanations for Yarn vs NPM** usage with specific
benefits
- ✅ **Improved code formatting** with bash syntax highlighting for
better readability

### Hermes Documentation
- ✅ **Added version-specific debugging support information** (RNW
v0.75+)
- ✅ **Linked to known issues**
([#12982](microsoft/react-native-windows#12982))
for transparency
- ✅ **Resolved contradiction** between debugging instructions and
limitations section

### Migration Guide
- ✅ **Added version context note** - applicable from RNW v0.74+ but
targets v0.80
- ✅ **Converted inline commands to proper bash code blocks** for better
copy-paste experience
- ✅ **Improved overall readability** and formatting consistency

## 🔧 Why These Changes Matter

1. **Reduces Setup Friction**: Clear prerequisites prevent users from
encountering issues mid-setup
2. **Improves Understanding**: Explanations help users understand what
each command does and why it's needed
3. **Sets Proper Expectations**: Version-specific information helps
users understand feature availability
4. **Better Developer Experience**: Proper code formatting makes
commands easier to copy and execute
5. **Eliminates Confusion**: Resolves contradictory information about
debugging capabilities

## 📚 Files Changed

- `website/versioned_docs/version-0.80/getting-started.md` - Enhanced
setup instructions and prerequisites
- `website/versioned_docs/version-0.80/hermes.md` - Added
version-specific debugging information
- `website/versioned_docs/version-0.80/migration-guide.md` - Improved
command formatting and version context

## ✅ Addresses PR Review Comments

- Enhanced command explanations per reviewer feedback
- Added version-specific information for Hermes debugging support
- Improved code formatting consistency across all documentation guides
- Added clear context about version compatibility and limitations



###### Microsoft Reviewers: [Open in
CodeFlow](https://microsoft.github.io/open-pr/?codeflow=https://github.com/microsoft/react-native-windows-samples/pull/1093)

Author: anupriya13

.spelling

@@ -168,4 +168,6 @@ rtl
 e.g.numeric
 ascii-capable
 url
-VSCode
+VSCode
+v0.80
+v0.74

website/versioned_docs/version-0.61/rnm-getting-started.md

@@ -10,7 +10,7 @@ For information around how to set up:
 - React Native for iOS and Android: See [React Native Getting Started Guide](https://reactnative.dev/docs/getting-started)
 - React Native for Windows: See [React Native for Windows Getting Started Guide](https://microsoft.github.io/react-native-windows/docs/getting-started)
 
-Make sure you have installed all the [development dependencies](https://microsoft.github.io/react-native-windows/docs/rnm-dependencies)
+Make sure you have installed all of the [development dependencies](https://microsoft.github.io/react-native-windows/docs/rnw-dependencies).
 
 ## Install React Native for macOS
 

website/versioned_docs/version-0.62/rnm-getting-started.md

@@ -10,7 +10,7 @@ For information around how to set up:
 - React Native for iOS and Android: See [React Native Getting Started Guide](https://reactnative.dev/docs/getting-started)
 - React Native for Windows: See [React Native for Windows Getting Started Guide](https://microsoft.github.io/react-native-windows/docs/getting-started)
 
-Make sure you have installed all the [development dependencies](https://microsoft.github.io/react-native-windows/docs/rnm-dependencies)
+Make sure you have installed all of the [development dependencies](https://microsoft.github.io/react-native-windows/docs/rnw-dependencies).
 
 ## Install React Native for macOS
 

website/versioned_docs/version-0.63/rnm-getting-started.md

@@ -10,7 +10,7 @@ For information around how to set up:
 - React Native for iOS and Android: See [React Native Getting Started Guide](https://reactnative.dev/docs/getting-started)
 - React Native for Windows: See [React Native for Windows Getting Started Guide](https://microsoft.github.io/react-native-windows/docs/getting-started)
 
-Make sure you have installed all the [development dependencies](https://microsoft.github.io/react-native-windows/docs/rnm-dependencies)
+Make sure you have installed all of the [development dependencies](https://microsoft.github.io/react-native-windows/docs/rnw-dependencies).
 
 ## Install React Native for macOS
 

website/versioned_docs/version-0.64/rnm-getting-started.md

@@ -10,7 +10,7 @@ For information around how to set up:
 - React Native for iOS and Android: See [React Native Getting Started Guide](https://reactnative.dev/docs/getting-started)
 - React Native for Windows: See [React Native for Windows Getting Started Guide](https://microsoft.github.io/react-native-windows/docs/getting-started)
 
-Make sure you have installed all the [development dependencies](https://microsoft.github.io/react-native-windows/docs/rnm-dependencies)
+Make sure you have installed all of the [development dependencies](https://microsoft.github.io/react-native-windows/docs/rnw-dependencies).
 
 ## Install React Native for macOS
 

website/versioned_docs/version-0.66/rnm-getting-started.md

@@ -10,7 +10,7 @@ For information around how to set up:
 - React Native for iOS and Android: See [React Native Getting Started Guide](https://reactnative.dev/docs/getting-started)
 - React Native for Windows: See [React Native for Windows Getting Started Guide](https://microsoft.github.io/react-native-windows/docs/getting-started)
 
-Make sure you have installed all the [development dependencies](https://microsoft.github.io/react-native-windows/docs/rnm-dependencies)
+Make sure you have installed all of the [development dependencies](https://microsoft.github.io/react-native-windows/docs/rnw-dependencies).
 
 ## Install React Native for macOS
 

website/versioned_docs/version-0.68/rnm-getting-started.md

@@ -10,7 +10,7 @@ For information around how to set up:
 - React Native for iOS and Android: See [React Native Getting Started Guide](https://reactnative.dev/docs/getting-started)
 - React Native for Windows: See [React Native for Windows Getting Started Guide](https://microsoft.github.io/react-native-windows/docs/getting-started)
 
-Make sure you have installed all the [development dependencies](https://microsoft.github.io/react-native-windows/docs/rnm-dependencies)
+Make sure you have installed all of the [development dependencies](https://microsoft.github.io/react-native-windows/docs/rnw-dependencies).
 
 ## Install React Native for macOS
 

website/versioned_docs/version-0.80/getting-started.md

@@ -16,6 +16,8 @@ For information around how to set up React Native, see the [React Native Getting
 
 ## Create a new React Native project
 
+> **Prerequisites:** Before creating your React Native for Windows project, ensure you have completed all the [development dependencies setup](rnw-dependencies.md). This includes installing Visual Studio with the required workloads, Windows SDK, Node.js, and other essential tools.
+
 Call the following from the place where you want your project directory to live:
 
 <!-- Note, make sure both `@react-native-community/cli@ABC` and `--version "XYZ"` are pointing to the correct NPM tags in the command below. -->
@@ -45,18 +47,22 @@ cd <projectName>
 <!-- 1. For the next version (i.e. in docs/getting-started.md) use "canary" -->
 <!-- 2. For other versions in versioned_docs use the version in the format "^0.XY.0" -->
 
-Next you'll want to add `react-native-windows` as a dependency:
+Next you'll want to add `react-native-windows` as a dependency. This step adds the React Native for Windows platform-specific implementation to your project, which provides the Windows-specific native components, modules, and build tools needed to run your React Native app on Windows.
 
 <!--DOCUSAURUS_CODE_TABS-->
 
 <!--Using Yarn (Recommended)-->
 
+This command uses Yarn to add the React Native for Windows package to your project's dependencies. Yarn provides faster and more reliable dependency management:
+
 ```bat
 yarn add react-native-windows@^0.80.0
 ```
 
 <!--Using NPM-->
 
+This command uses NPM to install and save the React Native for Windows package to your project's dependencies. The `--save` flag ensures the package is added to your `package.json` file:
+
 ```bat
 npm install --save react-native-windows@^0.80.0
 ```
@@ -65,7 +71,7 @@ npm install --save react-native-windows@^0.80.0
 
 ### Initialize the React Native Windows native code and projects
 
-Lastly, initialize the React Native for Windows application with the [init-windows command](init-windows-cli.md):
+Lastly, initialize the React Native for Windows application with the [init-windows command](init-windows-cli.md). This command generates the Windows-specific native project files, including Visual Studio solution files, C++ or C# project templates, and platform-specific configuration needed to build and run your app on Windows:
 
 ```bat
 npx react-native init-windows --overwrite
@@ -99,9 +105,9 @@ npx react-native init-windows --overwrite
   - Run `yarn start` (or `npm start`) from your project directory, and wait for the React Native packager to report success.
   - Click the `Run` button to the right of the platform combo box control in VS, or select the `Debug`->`Start without Debugging` menu item. You now see your new app and Chrome should have loaded `http://localhost:8081/debugger-ui/` in a new tab. Press `F12` or `Ctrl+Shift+I` in Chrome to open its Developer Tools. :tada:
 
-- With VS Code
-  - Open your applications folder in VS Code.
-  - Install the [React Native Tools](https://marketplace.visualstudio.com/items?itemName=msjsdiag.vscode-react-native) plugin for VS Code.
+- With Visual Studio Code
+  - Open your applications folder in Visual Studio Code.
+  - Install the [React Native Tools](https://marketplace.visualstudio.com/items?itemName=msjsdiag.vscode-react-native) plugin for Visual Studio Code.
   - Create a new file in the applications root directory, `.vscode/launch.json` and paste the following configuration:
   ```json
   {

website/versioned_docs/version-0.80/hermes.md

@@ -90,6 +90,8 @@ Follow steps 1-7 from above, and then
 
 ### Enable debugging/profiling on release builds
 
+> **Note:** Hermes debugging support varies by React Native Windows version. Direct debugging with Hermes inspector is supported in React Native Windows 0.75+ but has [known issues](https://github.com/microsoft/react-native-windows/issues/12982) in certain versions. Check the [Known Issues](#known-issues) section below for current debugging limitations in this version.
+
 We keep the inspector turned off on release builds by default. If you want to debug or profile release builds, set the MSBuild property `EnableHermesInspectorInReleaseFlavor` to `'true'` when building the platform with the [run-windows command](run-windows-cli.md), i.e.:
 
 ```bash
@@ -99,5 +101,5 @@ npx react-native run-windows --msbuildprops EnableHermesInspectorInReleaseFlavor
 ### Known Issues
 
 1. CPU Sampling profiler currently doesn't work.  
-2. Debugging and related activities (including Chrome/Edge DevTools, VSCode debugger) are currently non-functional.  
+2. Debugging and related activities (including Chrome/Edge DevTools, Visual Studio Code debugger) are currently non-functional.  
    - Issue under investigation for React Native Windows Hermes runtime.  

website/versioned_docs/version-0.80/migration-guide.md

@@ -13,6 +13,8 @@ original_id: migration-guide
 
 React Native 0.80 introduces Fabric as the default renderer and completes the transition to the New Architecture (Fabric + TurboModules). For React Native Windows (RNW), this migration replaces the legacy Paper architecture with a modern rendering pipeline that improves performance and memory usage. 
 
+> **Note:** This documentation references RNW v0.80, since Fabric becomes the default renderer starting with this version. However, the migration guide can be generally referred to for migrating from Paper to Fabric beginning with RNW versions supporting Fabric (starting RNW v0.74).
+
 ### Key Concepts 
 
 
@@ -37,7 +39,7 @@ React Native 0.80 introduces Fabric as the default renderer and completes the tr
 
 Run yarn install after every update of package.json file 
 
-### Calculator App Migration 
+### RNW App Migration 
 
 About the App: 
 
@@ -55,17 +57,37 @@ Before you migrate confirm few things on your Paper project re-confirm that your
 
 
 ### Steps Followed to Migrate to New Architecture (Fabric) 
-- Upgrade Dependencies: Update package.json to use React Native 0.80 and run `npm install` or `yarn install`. (Reference - [react-native-windows-samples/samples/Calculator/cppwinrt/package.json at 9e5d850e843acc2ff060fbd64673511cc67265f9 · microsoft/react-native-windows-samples](https://github.com/microsoft/react-native-windows-samples/blob/9e5d850e843acc2ff060fbd64673511cc67265f9/samples/Calculator/cppwinrt/package.json))  
-
-- Delete the Existing Windows Directory / Run `rm -rf windows` to remove the legacy project files. 
+- Upgrade Dependencies: Update package.json to use React Native 0.80 and run:
+  ```bash
+  npm install
+  ```
+  or
+  ```bash
+  yarn install
+  ```
+  (Reference - [react-native-windows-samples/samples/Calculator/cppwinrt/package.json at 9e5d850e843acc2ff060fbd64673511cc67265f9 · microsoft/react-native-windows-samples](https://github.com/microsoft/react-native-windows-samples/blob/9e5d850e843acc2ff060fbd64673511cc67265f9/samples/Calculator/cppwinrt/package.json))  
+
+- Delete the Existing Windows Directory:
+  ```bash
+  rm -rf windows
+  ```
 
 - Update Template in package.json: Set `"template": "cpp-app"` to use the new architecture template. 
 
-- Run yarn install 
+- Run:
+  ```bash
+  yarn install
+  ```
 
-- Reinitialize the Windows Project: Run `npx react-native init-windows --template cpp-app` to generate Fabric-compatible project files. 
+- Reinitialize the Windows Project:
+  ```bash
+  npx react-native init-windows --template cpp-app
+  ```
 
-- Run the Application: Use `npx @react-native-community/cli run-windows` to launch the Fabric app. 
+- Run the Application:
+  ```bash
+  npx @react-native-community/cli run-windows
+  ``` 
 
 
 You will see new files created / updated inside windows directory 
@@ -79,16 +101,27 @@ Commit Paper to Fabric: [migrate calculator by anupriya13 · Pull Request #1092
 
 In case you encounter issues migrating to Fabric or due to unsupported controls or properties in Fabric please refer to below steps to revert back to Paper architecture. If you encounter missing properties, please open an issue: https://github.com/microsoft/react-native-windows/issues 
 
-
-- Delete the Windows Directory / Run `rm -rf windows`. 
+- Delete the Windows Directory:
+  ```bash
+  rm -rf windows
+  ```
 
 - Update Template in package.json: Set `"template": "old/uwp-cpp-app"`. (Reference -[react-native-windows-samples/samples/Calculator/fabric/package.json at 9e5d850e843acc2ff060fbd64673511cc67265f9 · microsoft/react-native-windows-samples](https://github.com/microsoft/react-native-windows-samples/blob/9e5d850e843acc2ff060fbd64673511cc67265f9/samples/Calculator/fabric/package.json)) 
 
-- Run "yarn" 
+- Run:
+  ```bash
+  yarn
+  ```
 
-- Reinitialize the Old Architecture Project: Run `npx react-native init-windows --template old/uwp-cpp-app`. 
+- Reinitialize the Old Architecture Project:
+  ```bash
+  npx react-native init-windows --template old/uwp-cpp-app
+  ```
 
-- Run the App: Execute `npx @react-native-community/cli run-windows` to start the Paper-based app. 
+- Run the App:
+  ```bash
+  npx @react-native-community/cli run-windows
+  ``` 
 
 
 
@@ -112,4 +145,4 @@ In the New Architecture RNW, the Flyout and Popup components have been updated t
 
 ### Conclusion 
 
-Migrating from Paper to Fabric in React Native Windows 0.80 modernizes your project, improves performance, and prepares your app for future React Native releases. Reverting to the old architecture is simple if required.
+Migrating from Paper to Fabric in React Native Windows modernizes your project, improves performance, and prepares your app for future React Native releases. Reverting to the old architecture is simple if required.