Skip to content

Commit f474d2e

Browse files
author
Timo Stark
committed
Update Wording
1 parent e44d425 commit f474d2e

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

source/news/2024/index.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ News archive for the year 2024.
1616
.. nxt_news_entry::
1717
:author: Timo Stark
1818
:description: Part 1 of 2 of our Wasm Compoent Model blog seires and a deep dive into the
19-
Wasm Component Model it's ecosytem and how eveything came to life on NGINX Unit.
19+
Wasm Component Model, it's ecosytem and how eveything came to life on NGINX Unit.
2020
2121
:title: The WebAssembly Component Model - Part 1
2222
:url: news/2024/wasm-component-model-part-1

source/news/2024/wasm-component-model-part-1.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ We have done just that with Unit 1.32.0. This release supports Wasm Components u
2424

2525
Let's pause here for a moment. If the previous sentence contained unfamiliar vocabulary, don't worry. This blog post will explain the concept of the Component Model for WebAssembly (Wasm) and the role that the WebAssembly System Interface (WASI) plays in this context. We will also discuss the significance of the "WebAssembly Interface Types."
2626

27-
As you can read in our first `Wasm Blog Post <https://www.nginx.com/blog/server-side-webassembly-nginx-unit/>`__ , the Wasm runtime shares data with the Wasm Module as raw bytes over shared memory. To make sense of this byte stream, the Host as well as the Wasm Module must speak about the same things or technically speaking, implementing the same interfaces. It is a core concept of NGINX Unit to create an application-specific context of an incoming HTTP request and share this set of bytes in memory with the runtime.
27+
As you can read in our first `Wasm blog post <https://www.nginx.com/blog/server-side-webassembly-nginx-unit/>`__ , the Wasm runtime shares data with the Wasm Module as raw bytes over shared memory. To make sense of this byte stream, the Host as well as the Wasm Module must speak about the same things or technically speaking, implementing the same interfaces. It is a core concept of NGINX Unit to create an application-specific context of an incoming HTTP request and share this set of bytes in memory with the runtime.
2828

2929
This is exactly what we did with **unit-wasm** and it was an interesting and necessary learning to add Wasm support to Unit. However, this is far away from implementing or using a standard. This is where the Wasm Component Model comes into play.
3030

source/news/2024/wasm-component-model-part-2.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
The WebAssembly Component Model - The Why, How and What - Part 2
55
##################################################################
66

7-
This is Part 2 of our Blog series about the Wasm Component Model, it's ecosytem and how to use Wasm Components with NGINX Unit.
7+
This is Part 2 of our blog series about the Wasm Component Model, it's ecosytem and how to use Wasm Components with NGINX Unit.
88
In `Part 1 </news/2024/wasm-component-model-part-1>`__ we have covered all the conceptional parts. In this part, we will focus on the process of creating a Wasm Component.
99

1010
************************************************************************

0 commit comments

Comments
 (0)