Skip to content

Commit 6398cb5

Browse files
authored
Apply suggestion from @maartenba
1 parent 277df92 commit 6398cb5

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

src/content/docs/bff/upgrading/bff-v3-to-v4.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -133,13 +133,13 @@ var frontend = new BffFrontend(BffFrontendName.Parse("frontend1"))
133133
.WithCdnIndexHtml(new Uri("https://my_cdn/some_app/index.html"))
134134
```
135135

136-
When you do this, the BFF automatically wires up a catch-all route that serves the `index.html` for that specific frontend.
136+
The BFF automatically wires up a catch-all route that serves`index.html` for that specific frontend.
137+
137138
See [Serve the index page from the BFF host](/bff/architecture/ui-hosting.md#serve-the-index-page-from-the-bff-host) for more information.
138139

139-
### Proxying all static assets
140+
### Proxying All Static Assets
140141

141-
When developing a SPA based application, it's very common to use a development webserver such as Vite. While vite can publish static assets with a 'base',
142-
this doesn't work well during development.
142+
When developing a Single-Page Application (SPA), it's very common to use a development webserver such as Vite. While Vite can publish static assets with a base URL, this doesn't work well during development.
143143

144144
The best development experience can be achieved by configuring the BFF to proxy all static assets from the development server:
145145

0 commit comments

Comments
 (0)