Being a technical writer at Grafana Labs can be unexpectedly adventurous, as illustrated by the author's experience with testing Grafana installation documentation on Windows and Linux. While attempting to install a plugin on both operating systems, the author encountered permission issues on Windows that were resolved by running PowerShell as an Administrator, highlighting a gap in the documentation. Further challenges arose when the author discovered a Linux command mistakenly included in the Windows instructions and undocumented global options in the Grafana CLI. These experiences led to updates in the documentation, emphasizing the dynamic nature of technical writing which involves constant problem-solving and collaboration with developers. The author concludes by inviting suggestions for further documentation improvements, showcasing the ongoing journey of refining technical content.