From 3814a56d48e9eb5c31f62e2d48cbe8d1379fa869 Mon Sep 17 00:00:00 2001 From: David Sanders Date: Thu, 5 Nov 2020 14:11:38 -0800 Subject: [PATCH] chore: fix markdown in docs (#26357) --- docs/development/build-instructions-gn.md | 2 +- docs/tutorial/performance.md | 2 +- docs/tutorial/windows-arm.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/development/build-instructions-gn.md b/docs/development/build-instructions-gn.md index 50873b4c8c17..d8fb0ef234ef 100644 --- a/docs/development/build-instructions-gn.md +++ b/docs/development/build-instructions-gn.md @@ -53,7 +53,7 @@ $ gclient sync --with_branch_heads --with_tags > Instead of `https://github.com/electron/electron`, you can use your own fork > here (something like `https://github.com//electron`). -#### A note on pulling/pushing +### A note on pulling/pushing If you intend to `git pull` or `git push` from the official `electron` repository in the future, you now need to update the respective folder's diff --git a/docs/tutorial/performance.md b/docs/tutorial/performance.md index c3533af62474..f90bd99b9e0f 100644 --- a/docs/tutorial/performance.md +++ b/docs/tutorial/performance.md @@ -104,7 +104,7 @@ connectivity checks included in later versions of Chromium. When considering a module, we recommend that you check: 1. the size of dependencies included -2) the resources required to load (`require()`) it +2. the resources required to load (`require()`) it 3. the resources required to perform the action you're interested in Generating a CPU profile and a heap memory profile for loading a module can be done diff --git a/docs/tutorial/windows-arm.md b/docs/tutorial/windows-arm.md index a169871c7fb0..f7895c5af6c2 100644 --- a/docs/tutorial/windows-arm.md +++ b/docs/tutorial/windows-arm.md @@ -89,7 +89,7 @@ Debugging native modules can be done with Visual Studio 2017 (running on your de 3. Connect to the target device by selecting _Debug > Attach to Process..._ and enter the device's IP address and the port number displayed by the Visual Studio Remote Debugger tool. 4. Click _Refresh_ and select the [appropriate Electron process to attach](../development/debug-instructions-windows.md). 5. You may need to make sure that any symbols for native modules in your app are loaded correctly. To configure this, head to _Debug > Options..._ in Visual Studio 2017, and add the folders containing your `.pdb` symbols under _Debugging > Symbols_. -5. Once attached, set any appropriate breakpoints and resume JavaScript execution using Chrome's [remote tools for Node](debugging-main-process.md). +6. Once attached, set any appropriate breakpoints and resume JavaScript execution using Chrome's [remote tools for Node](debugging-main-process.md). ## Getting additional help If you encounter a problem with this documentation, or if your app works when compiled for x86 but not for arm64, please [file an issue](../development/issues.md) with "Windows on Arm" in the title.