This update is a high pri request from Tod Edwards, Sr. Technical Advisor for Devices. Here is what he requested in the work item he filed with the CSS Content team:
-----------------------------------------------------------------------------------------------------------------------------------------------------
Update https://docs.microsoft.com/en-us/surface/microsoft-surface-brightness-control
Version 1.16.137 uses this registry location now:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Surface\Surface Brightness Control
We need to keep information on the page that says previous versions of the tool use:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Surface\Surface Brightness Control
If customer doesn't know which version they have, they will know which place they need to edit based on if the registry path exists or not, since the registry location is created when the app is installed.
as per user report #5756 , i removed the following sentence
> [!NOTE]
> A log file is not created by default. In order to create a log file, you will need to append "/l*v [path]"
* fixed issue with h1s from hotlinked note-articles rendering as duplicate h1s
* testing path is correct
* find & replace old path > new path
attempting to fix issue with note-articles not being in seperate /includes dir
* fixed link on note page
* Adding a sentence to dynamic lock
* Add titleSuffix for mdop
* Add titleSuffix for smb
* Add titleSuffix for surface-hub
* Add titleSuffix for Edge
* Add titleSufix for client-management
* Correct metadata attribute
* Add titleSuffix for application-management
* Add titleSuffix for surface
* Add titleSuffix for hub
* pencil edit
line 27
* Add titleSuffix for deployment
* pencil edit
line 27
* pencil edit
line 27
* pencil edit
line 27
* Add titleSuffix for internet-explorer
* Add titleSuffix for privacy
Also added one tab spacing for lines 43-47 for beautification
* Add titleSuffix for whats-new
* Add titleSuffix for security
* Add titleSuffix for configuration
* CAT Auto Pulish for Windows Release Messages - CAT_AutoPublish_20191210080851 (#1678)
@Dansimp
Please review the copy edit to this article and let me know if I’ve changed the technical meaning anywhere. Also, please ensure you've included all metadata values per Requirements, including localization priority.
This is the second of three PRs for DevOps work request 3805258.
Thanks!
Kelly
@dansimp – Here we go! Please review the copy edit to this article and let me know if I’ve changed the technical meaning anywhere. Also, should the proc heading on line 468 be step 3 instead of a sub-step of step 2? It's hard for me to tell.
This is the first of three PRs for DevOps work request 3805258.
Thanks!
Kelly
