some assets updates

Author: emily-shen

src/content/docs/workers/static-assets/index.mdx

@@ -59,6 +59,10 @@ The **assets directory** specified in your [Wrangler configuration file](/worker
 
 </WranglerConfig>
 
+:::note
+With some build/development tools, including the Cloudflare Vite plugin, you don't need to specify `assets.directory`. This field is functionally equivalent to the build output folder.
+:::
+
 By adding an [**assets binding**](/workers/static-assets/binding/#binding), you can directly fetch and serve assets within your Worker code.
 
 ```js {13}
@@ -83,7 +87,7 @@ export default {
 
 By default, if a requested URL matches a file in the static assets directory, that file will always be served — without running Worker code. If no matching asset is found and a Worker is configured, the request will be processed by the Worker instead.
 
-- If no Worker is set up, the [`not_found_handling`](/workers/static-assets/routing/#2-not_found_handling-1) setting in your Wrangler configuration determines what happens next. By default, a `404 Not Found` response is returned.
+- If no Worker is set up, the [`not_found_handling`](/workers/static-assets/routing/#not_found_handling-1) setting in your Wrangler configuration determines what happens next. By default, a `404 Not Found` response is returned.
 
 - If a Worker is configured and a request does not match a static asset, the Worker will handle the request. The Worker can choose to pass the request to the asset binding (through `env.ASSETS.fetch()`), following the `not_found_handling` rules.
 

src/content/docs/workers/wrangler/configuration.mdx

@@ -998,7 +998,7 @@ You can only configure one collection of assets per Worker.
 
 The following options are available under the `assets` key.
 
-- `directory` <Type text="string" /> <MetaInfo text="required" />
+- `directory` <Type text="string" /> <MetaInfo text="optional" />
 
   - Folder of static assets to be served.
   - Not required if you're using the [Cloudflare Vite plugin](/workers/local-development/vite/), which will automatically point to the client build output.