diff --git a/2016-09/NetflixMethodology.html b/2016-09/NetflixMethodology.html
index 7ca6870..e27f9a7 100644
--- a/2016-09/NetflixMethodology.html
+++ b/2016-09/NetflixMethodology.html
@@ -35,7 +35,7 @@
Computer setup
Ambient light sensor was temporarily disabled
All queued Ngen complication jobs were completed
Windows update was temporarily disabled
- “New network found” prompts were disabled
+ "New network found" prompts were disabled
Windows Error Reporting was temporarily disabled
Queued idle tasks were forced to complete
Defender was running normally and up to date
diff --git a/2016-09/VimeoMethodology.html b/2016-09/VimeoMethodology.html
index 11c63a3..18669a3 100644
--- a/2016-09/VimeoMethodology.html
+++ b/2016-09/VimeoMethodology.html
@@ -35,7 +35,7 @@ Computer setup
Ambient light sensor was temporarily disabled
All queued Ngen complication jobs were completed
Windows update was temporarily disabled
- “New network found” prompts were disabled
+ "New network found" prompts were disabled
Windows Error Reporting was temporarily disabled
Queued idle tasks were forced to complete
Defender was running normally and up to date
diff --git a/2016-09/WebdriverMethodology.html b/2016-09/WebdriverMethodology.html
index 23463b6..9fcc7c6 100644
--- a/2016-09/WebdriverMethodology.html
+++ b/2016-09/WebdriverMethodology.html
@@ -38,7 +38,7 @@ Computer setup
Ambient light sensor was temporarily disabled
All queued Ngen complication jobs were completed
Windows update was temporarily disabled
- “New network found” prompts were disabled
+ "New network found" prompts were disabled
Windows Error Reporting was temporarily disabled
Queued idle tasks were forced to complete
Defender was running normally and up to date
@@ -88,12 +88,12 @@ Activites and automation harness
Note that pauses are included throughout this workload, but are not included in this description for simplicity. Each scenario (one domain in one tab) lasts about a minute before the next tab is opened, though it varies by scenario.
- Open the respective browser
- - Navigate to a video on Youtube.com: “Microsoft Design: Connecting Makers”
+ - Navigate to a video on Youtube.com: "Microsoft Design: Connecting Makers"
- The video will autoplay and will continue in a background tab for the remainder of the test
- Open a new tab
- In the new tab, navigate to amazon.com
- - In the search box, enter “Game of Thrones” and press enter
- - Click on “Game of Thrones Season 1”
+ - In the search box, enter "Game of Thrones" and press enter
+ - Click on "Game of Thrones Season 1"
- Scroll down to the reviews
- Open a new tab
- In the new tab, navigate to Facebook.com
@@ -101,13 +101,13 @@ Activites and automation harness
- Scroll through the feed on Facebook
- Open a new tab
- In the new tab, navigate to google.com
- - Search for “Seattle”
+ - Search for "Seattle"
- Open a new tab
- In the new tab, navigate to gmail.com
- Log in to Gmail
- Open and then close several messages in the inbox
- Open a new tab
- - In the new tab, navigate to the Wikipedia article on “United States”
+ - In the new tab, navigate to the Wikipedia article on "United States"
- Scroll through the article
- Close the browser
@@ -115,7 +115,7 @@ Activites and automation harness
The code used to execute the test can be found on Github.
Measuring power
- Power was measured on the Surface Book because it has integrated hardware instrumentation that’s able to measure the real power consumption of the CPU, GPU and Wifi antenna while the automation is being executed. This is done using the Maxim 34407 Power Accumulator chip. The results of the Maxim chips were read using the built in Windows tool “Performance Monitor”. Performance Monitor was opened and configured to measure each component independently:
+ Power was measured on the Surface Book because it has integrated hardware instrumentation that's able to measure the real power consumption of the CPU, GPU and Wifi antenna while the automation is being executed. This is done using the Maxim 34407 Power Accumulator chip. The results of the Maxim chips were read using the built in Windows tool "Performance Monitor". Performance Monitor was opened and configured to measure each component independently:
- \Energy Meter (CPU_CORES)\Power
- \Energy Meter (GPU_TOP)\Power