Docs: refreshed concurrency docs, callout webhooks api (#1031)

* Update concurrency docs for clarity

* Callout the webhooks api

* Disable broken links for now until site is fixed

app/globals.css

@@ -143,7 +143,7 @@ body {
     --color-border-success: var(--color-matcha-700);
     --color-border-error: var(--color-ruby-600);
     --color-border-warning: var(--color-honey-600);
-    --color-border-info: var(--color-purplehaze-700);
+    --color-border-info: var(--color-breeze-600);
 
     --color-primary-2xSubtle: var(--color-matcha-200);
     --color-primary-xSubtle: var(--color-matcha-300);
@@ -247,7 +247,7 @@ body {
     --color-border-success: var(--color-matcha-500);
     --color-border-error: var(--color-ruby-300);
     --color-border-warning: var(--color-honey-300);
-    --color-border-info: var(--color-purplehaze-300);
+    --color-border-info: var(--color-breeze-300);
 
     --color-primary-2xSubtle: var(--color-matcha-800);
     --color-primary-xSubtle: var(--color-matcha-700);

pages/blog/[slug].tsx

@@ -107,7 +107,7 @@ const authorURLs = {
   "Taylor Facen": "https://twitter.com/ItsTayFay",
   "Igor Samokhovets": "https://twitter.com/IgorSamokhovets",
   "Dave Kiss": "https://twitter.com/davekiss",
-  "Bruno Scheufler": "https://brunoscheufler.com",
+  // "Bruno Scheufler": "https://brunoscheufler.com", // removed while site is disabled
   "Lydia Hallie": "https://x.com/lydiahallie",
   "Joe Adams": "https://www.linkedin.com/in/josephadams9/",
   "Charly Poly": "https://x.com/whereischarly",

pages/blog/_posts/sharding-at-inngest.mdx

@@ -32,7 +32,7 @@ Our first phase was to create a new interface layer that would coordinate how ou
 
 Two weeks after starting at Inngest, I joined forces with Jack Williams, our founding engineer, and kicked off work on a coordinator service mediating access to the state store. The state store persists events, step outputs, and other metadata on every function run. As users can return blobs and other data from their function run steps, we need to ensure incredibly fast reads and writes to the state store to keep latency as low as possible.
 
-Adding this service boundary would enable connection pooling, centralized instrumentation for observability, and a single cut-over point to roll out changes across different user segments. Long-term, this also allows us to replace the Redis-based storage backend with a more scalable system tailored to our access patterns. If you're interested in our work on the state coordinator, please check out [my recent post](https://brunoscheufler.com/blog/2024-07-04-enhancing-scalability-and-reducing-latency-without-missing-a-beat) on the design decisions and rollout strategy we chose.
+Adding this service boundary would enable connection pooling, centralized instrumentation for observability, and a single cut-over point to roll out changes across different user segments. Long-term, this also allows us to replace the Redis-based storage backend with a more scalable system tailored to our access patterns. {/* (NOTE Hidden until Bruno's site is back online)  If you're interested in our work on the state coordinator, please check out [my recent post](https://brunoscheufler.com/blog/2024-07-04-enhancing-scalability-and-reducing-latency-without-missing-a-beat) on the design decisions and rollout strategy we chose. */}
 
 ## Sharding Redis