From 50131748d4836eeedf525e0656823924b90db381 Mon Sep 17 00:00:00 2001
From: Erik Sundell <erik.i.sundell@gmail.com>
Date: Fri, 12 Apr 2024 07:59:43 +0200
Subject: [PATCH] docs: detail inline heading update

Co-authored-by: Georgiana <georgiana.dolocan@gmail.com>
---
 dashboards/cluster.jsonnet | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dashboards/cluster.jsonnet b/dashboards/cluster.jsonnet
index a6fb2ef..cca5b29 100755
--- a/dashboards/cluster.jsonnet
+++ b/dashboards/cluster.jsonnet
@@ -150,7 +150,7 @@ local nodepoolCPUCommitment =
       Most commonly, JupyterHub workloads are *memory bound*, not CPU bound. So this is
       not a particularly helpful graph.
 
-      Common shapes:
+      Common shapes this visualization may take:
       1. If this is *consistently high* but shaped differently than your memory commitment
         graph, consider changing your CPU requirements.
     |||