Fix minor typos

content/docs/getting-started/deployment.md

@@ -49,7 +49,7 @@ Zenoh applications in `peer` mode join multicast group `224.0.0.224` on UDP port
 
 **Gossip scouting**
 
-Zenoh applications in `peer` mode forward all local applications and router they already discovered to newly scouted applications. This is useful when multicast communications are not available. But applications need to connect to a first entry point to discover the rest of the system. This entry point is typically one or several Zenoh routers but can also be one or several other peers. Those entry points are configured through the `connect` section of the configuration.
+Zenoh applications in `peer` mode forward all local applications and routers they have already discovered to newly scouted applications. This is useful when multicast communications are not available. But applications need to connect to a first entry point to discover the rest of the system. This entry point is typically one or several Zenoh routers but can also be one or several other peers. Those entry points are configured through the `connect` section of the configuration.
 
 **Configuration**
 ```

content/docs/manual/abstractions.md

@@ -179,8 +179,8 @@ Since there exist many ways to implement the storing part of the process, the `s
 
 ## Admin space
 
-The key space of Zenoh dedicate to administer a Zenoh router and its plugins.
-It is accessible via regular get/put on Zenoh, under the `@/router/<router-id>` prefix, where
+The key space of Zenoh dedicated to administering a Zenoh router and its plugins.
+It is accessible via regular GET/PUT on Zenoh, under the `@/router/<router-id>` prefix, where
 **`<router-id>`** is the UUID of a Zenoh router.
 
 When using the REST API, you can replace the `<router-id>` with the **`local`** keyword,

content/docs/manual/configuration.md

@@ -66,7 +66,7 @@ The configuration of a Zenoh router can be changed at runtime via its admin spac
 ```
  - either via the `zenohd` command line option: `--adminspace-permissions <[r|w|rw|none]>`
 
-Then you can change elements of it's configuration once it's started, by sending put messages to its [admin space](../abstractions#admin-space).
+Then you can change elements of it's configuration once it's started, by sending PUT messages to its [admin space](../abstractions#admin-space).
 
 If one of the `zenohd` instances uses the REST plugin to expose Zenoh to HTTP requests, this can be done simply by sending such requests with tools such as `curl`.  
 To do this, use commands such as 

content/docs/manual/plugin-http.md

@@ -15,4 +15,4 @@ The REST plugin provides access to the Zenoh [REST API](../../apis/rest/) by ena
 There are two main ways to start this plugin:
 - **Through startup arguments**: `zenohd`'s `--rest-http-port=[PORT | IP:PORT | none]` argument allows you to choose which port will be listened to by the HTTP server. Note that the default value for this argument is `8000`, meaning that unless you specify `none` explicitly, `zenohd` will use this plugin by default.
 
-- **Through configuration:**: you may also configure the rest plugin in a `zenohd` config file, as illustrated in the Zenoh repo's [DEFAULT_CONFIG.json5 file](https://github.com/eclipse-zenoh/zenoh/blob/master/DEFAULT_CONFIG.json5)
+- **Through configuration**: you may also configure the rest plugin in a `zenohd` config file, as illustrated in the Zenoh repo's [DEFAULT_CONFIG.json5 file](https://github.com/eclipse-zenoh/zenoh/blob/master/DEFAULT_CONFIG.json5)