fix more docs

Author: makspll

docs/src/Summary/customizing-script-contexts.md

@@ -33,7 +33,7 @@ use bevy::prelude::*;
 use bevy_mod_scripting::prelude::*;
 fn scripting_plugin(app: &mut App) {
     app.add_plugins(LuaScriptingPlugin::default()
-                       .add_context_pre_handling_initializer(|context_key: &ContextKey, entity: Entity, context: &mut Lua| {
+                       .add_context_pre_handling_initializer(|context_key: &ContextKey, context: &mut Lua| {
         let globals = context.globals();
         if let Some(script_id) = context_key.script_id.as_ref() {
             globals.set("script_name", script_id.to_owned());

docs/src/Summary/running-scripts.md

@@ -25,15 +25,13 @@ Be wary of path separators, by default script ID's are derived from asset paths,
 
 ## Making static scripts runnable
 
-Some scripts do not require attaching to an entity. You can run these scripts by loading them first as you would with any other script, then either adding them at app level via `add_static_script` or by issuing a `AddStaticScript` command like so:
+Some scripts do not require attaching to an entity. You can run these scripts by loading them first as you would with any other script, then either adding them by issuing a `AttachScript` command like so:
 
 ```rust,ignore
-    commands.queue(AddStaticScript::new(my_script_handle));
+    commands.queue(AttachScript::new(script_attachment));
 ```
 
-The script will then be run as any other script but without being attached to any entity. and as such the `entity` global will always represent an invalid entity.
-
-Note: Internally these scripts are attached to a dummy entity and as such you can think of them as being attached to an entity with an id of `0`.
+The script will then be run as any other script but without being attached to any entity.
 
 # Running Scripts