editorial pass

Author: anupras-mohapatra-arm

content/learning-paths/mobile-graphics-and-gaming/neural-graphics-playbook-evaluate/01-from-neural-graphics-to-megalights.md

@@ -10,19 +10,19 @@ layout: learningpathall
 
 When we first started talking about neural graphics at Arm, the idea was pretty simple: if some parts of rendering can be done more efficiently with machine learning, that frees up budget for everything else. At SIGGRAPH 2025, we announced that [Arm GPUs will have dedicated neural accelerators (NX) in 2026](https://newsroom.arm.com/news/arm-announces-arm-neural-technology). Since then, we’ve worked hard to build the tools that developers will need to seamlessly evaluate and integrate neural graphics use cases.
 
-On mobile, every rendering decision is a tradeoff. Resolution, lighting, effects, frame rate, thermals, battery life—they all compete for the same limited resources. And ultimately, those technical tradeoffs affect something even more important: the player experience. Visual quality matters, but so does responsiveness, stable performance, and how long a player can stay immersed in the game without the device heating up or throttling.
+On mobile, every rendering decision is a tradeoff. Resolution, lighting, effects, frame rate, thermals, battery life all compete for the same limited resources. Ultimately, those technical tradeoffs affect something even more important: the player experience. Visual quality matters, but so does responsiveness, stable performance, and how long a player can stay immersed in the game without their device heating up or throttling.
 
-[Neural Super Sampling (NSS)](https://developer.arm.com/community/arm-community-blogs/b/mobile-graphics-and-gaming-blog/posts/how-to-access-arm-neural-super-sampling) was our first attempt at shifting that balance. Upscaling itself isn’t new. Shader-based upscalers are already widely used across game engines and mobile games because rendering at lower resolution is one of the most effective ways to save performance. What interested us was whether machine learning could push that idea further.
+[Neural Super Sampling (NSS)](https://developer.arm.com/community/arm-community-blogs/b/mobile-graphics-and-gaming-blog/posts/how-to-access-arm-neural-super-sampling) was our first attempt at shifting that balance. Upscaling isn’t new. Shader-based upscalers are already widely used across game engines and mobile games because rendering at lower resolution is one of the most effective ways to save performance. What interested us was whether machine learning could push that idea further.
 
-In practice, NSS allowed us to work with more aggressive upscale ratios, like rendering at 540p and reconstructing to 1080p, while maintaining image quality that would be difficult to achieve with more traditional approaches. It also opened up better NX utilization in Arm GPUs, while reducing pressure on bandwidth and energy consumption, which are often just as important to mobile developers as raw frame rate.
+In practice, NSS allowed us to work with more aggressive upscale ratios, such as rendering at 540p and reconstructing to 1080p, while maintaining image quality that would be difficult to achieve with more traditional approaches. It also opened up better NX utilization in Arm GPUs, while reducing pressure on bandwidth and energy consumption, which are often just as important to mobile developers as raw frame rate.
 
 On mobile, bandwidth is expensive. Moving less data around the system can have a major impact on power efficiency and sustained performance. In many cases, that becomes just as valuable as the rendering speedup itself.
 
 NSS was really a first step in exploring a bigger question: what happens if machine learning becomes a normal part of the rendering pipeline?
 
 ## From a single technique to something you can actually build on
 
-This has resulted in the Neural Graphics Development Kit - a set of Vulkan based tools to support early experimentation of different neural graphics use cases that are production ready and efficient for mobile.
+Exploring this question has resulted in the Neural Graphics Development Kit - a set of Vulkan based tools to support early experimentation of different neural graphics use cases that are production ready and efficient for mobile.
 
 | Resource |
 |----------|
@@ -33,19 +33,19 @@ This has resulted in the Neural Graphics Development Kit - a set of Vulkan based
 | [ML Emulation Layer for Vulkan](https://github.com/arm/ai-ml-emulation-layer-for-vulkan) |
 | [Neural Graphics Model Gym](https://github.com/arm/neural-graphics-model-gym) |
 
-The development kit, the Unreal plugin, the sample content—those are provided so you can get started with minimal effort and validate how it behaves with your own content. And that’s really the point. It’s one thing to show a clean before-and-after in a controlled scene, and something else entirely when you’re dealing with dynamic lighting, fast camera movement, complex materials, and all the edge cases that come with real production conditions. That’s where things either hold up or start to break, and where you actually learn if a technique is useful.
+The development kit, the Unreal plugin, and sample content are provided so you can get started with minimal effort and validate how it behaves with your own content. And that’s really the point. It’s one thing to show a clean before-and-after in a controlled scene, and something else entirely when you’re dealing with dynamic lighting, fast camera movement, complex materials, and all the edge cases that come with real production conditions. That’s where things either hold up or start to break, and where you actually learn if a technique is useful.
 
-Since then, we’ve been expanding neural graphics use cases beyond NSS into applications of frame generation and ray denoising, while also making sure it can be integrated in real projects. This playbook will focus on the techniques we’ve worked on since then, but NSS remains relevant as the most straightforward way to start evaluating neural graphics in a real project.
+Since then, we’ve been expanding neural graphics use cases beyond NSS into applications of frame generation and ray denoising, while also making sure it can be integrated in real projects. This playbook focuses on the techniques we’ve worked on since then, but NSS remains relevant as the most straightforward way to start evaluating neural graphics in a real project.
 
 ## Why this matters now
 
-As engines like Unreal adopt more advanced techniques like ray tracing, new neural graphics use cases start to make sense in a practical way. Features like MegaLights make it possible to work with far more dynamic lights than before, without the cost scaling directly with the number of lights. The challenge is that these approaches rely on very low sample counts, which quickly introduce noise—especially on mobile.
+As engines such as Unreal adopt more advanced techniques such as ray tracing, new neural graphics use cases start to make sense in a practical way. Features such as MegaLights make it possible to work with far more dynamic lights than before, without the cost scaling directly with the number of lights. The challenge is that these approaches rely on very low sample counts, which quickly introduce noise, especially on mobile.
 
 Traditional denoisers and shader-based upscalers already help solve part of that problem. But as rendering pushes toward lower resolutions, fewer samples, and more dynamic lighting, reconstruction quality becomes harder to maintain. We’ve found that neural reconstruction allows us to push more aggressive upscale ratios, work with noisier inputs, and still produce stable, high-quality output. It also helps reduce bandwidth and energy pressure, which matters just as much as raw frame rate on mobile devices. More importantly, it starts making some of these newer rendering approaches practical on mobile in the first place.
 
 ## Enter Neural Dawn
 
-Neural Dawn is how we validate the use cases are production ready.
+Neural Dawn is how we validate that the use cases are production ready.
 
 It’s a mobile game created with Unreal Engine using Megalights, combined with the neural graphics work we’ve been developing. The goal was to build a real game and see what actually happens when you try to use this end to end. Where the integration feels natural, where it doesn’t, what kind of gains you get, and what trade-offs show up along the way.
 

content/learning-paths/mobile-graphics-and-gaming/neural-graphics-playbook-evaluate/02-neural-dawn.md

@@ -1,5 +1,5 @@
 ---
-title: "About Neural Dawn"
+title: About Neural Dawn
 weight: 3
 
 ### FIXED, DO NOT MODIFY
@@ -18,14 +18,14 @@ First, it had to look good, like _really_ good. The lighting fidelity and scene
 
 Second, it had to run efficiently. We targeted 60 FPS to meet modern expectations for smooth, responsive mobile gameplay.
 
-And third, it had to show what becomes possible when neural graphics and Arm NX are used together with approaches like MegaLights, on mobile.
+And third, it had to show what becomes possible when neural graphics and Arm NX are used together with approaches such as MegaLights, on mobile.
 
 Instead of optimizing a traditional graphics pipeline, we built one that depends on neural reconstruction. Neural Dawn is built around MegaLights. We render at low resolution tracing a low amount of rays per pixel, then rely on:
 
 - Neural Super Sampling Denoising (NSSD) to denoise and upscale the image
 - Neural Frame Rate Upscaling (NFRU) to generate intermediate frames
 
-So, the final result looks like a clean, high-resolution, smooth experience, even though we only rendered about 1/8 of the pixels directly.
+So, the final result looks like a clean, high-resolution, smooth experience, even though we rendered only about one-eighth of the pixels directly.
 
 Ultimately, Neural Dawn shows that neural graphics on mobile are production ready.
 
@@ -47,17 +47,17 @@ It also stacks well with other techniques. Overall, NFRU is a fairly predictable
 
 ### NSSD
 
-NSSD is about making noisy, low-cost rendering usable. If you’ve worked with ray tracing, you’ve seen the issue. At real-time budgets, you can only afford a few rays per pixel. That gives you a very noisy image. Traditional shader- based denoisers help, but can struggle in challenging scenarios (for example, translucent particles like fire or mist).
+NSSD is about making noisy, low-cost rendering usable. If you’ve worked with ray tracing, you’ve seen the issue. At real-time budgets, you can only afford a few rays per pixel. That gives you a very noisy image. Traditional shader- based denoisers help, but can struggle in challenging scenarios (for example, translucent particles such as fire or mist).
 
-Unlike shader-based approaches, which often process diffuse, specular, shadows, and other signals separately, NSSD uses a neural network to reconstruct the final lighting result directly. This allows NSSD to perform denoising and upscaling together in a single pass, reducing the need for multiple specialized denoising stages.
+Unlike shader-based approaches, which often process diffuse, specular, shadows, and other signals separately, NSSD uses a neural network to reconstruct the final lighting result directly. Doing so allows NSSD to perform denoising and upscaling together in a single pass, reducing the need for multiple specialized denoising stages.
 
-In practical terms, NSSD lets you achieve high-quality rendering with Raytracing. We validated NSSD with Project Dawn with the following setup:
+In practical terms, with NSSD, you can achieve high-quality rendering with Raytracing. We validated NSSD with Project Dawn with the following setup:
 
 Rendering at 540p and upscaling to 1080p, tracing 1 ray per pixel with MegaLights.
 
 Normally, lighting cost scales with scene complexity. More lights = more cost. With stochastic techniques, you can keep the cost roughly constant, but the image gets noisy. NSSD cleans up that noise after the fact and makes the content usable.
 
-That’s what enables things like:
+That’s what enables things such as:
 
 - lots of dynamic lights in a scene
 - soft shadows from all lights
@@ -76,6 +76,6 @@ NFRU and NSSD don’t compete—they sit at different levels:
 
 You can use NFRU without touching your content.
 
-You can’t really use NSSD that way—it depends on how your game looks and how much you’re willing to invest in getting good results.
+You can’t really use NSSD that way — it depends on how your game looks and how much you’re willing to invest in getting good results.
 
-That’s why most teams will start with NSS and NFRU, and treat NSSD as something to explore once they’re ready to go deeper. In the next section, you will learn what is really behind these technologies, and how we enable them through tooling.
+That’s why most teams will start with NSS and NFRU, and treat NSSD as something to explore when they’re ready to go deeper. In the next section, you'll learn what is really behind these technologies, and how we enable them through tooling.