docs: minor updates for consistency of landing pages

canonical · Nov 26, 2024 · 63f2e8b · 63f2e8b
1 parent f1daf39
commit 63f2e8b
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 6 deletions.
diff --git a/docs/explanation/index.md b/docs/explanation/index.md
@@ -5,7 +5,7 @@ These guides explain how Pebble works.
 
 ## Fundamentals
 
-Pebble works as a daemon, with state and configuration stored in the `$PEBBLE` directory.
+Pebble works as a daemon and a client, with state and configuration stored in the `$PEBBLE` directory.
 
 ```{toctree}
 :titlesonly:
@@ -15,9 +15,9 @@ General model <general-model>
 ```
 
 
-## Access to the daemon
+## Access to the API
 
-The daemon exposes an API that remote clients can connect to. By default, Pebble restricts access to some API endpoints based on the user that is connecting. You can set up named identities to grant specific access levels to users.
+The daemon exposes an API that clients can connect to. By default, Pebble restricts access to some API endpoints based on the user that is connecting. You can set up named "identities" to grant specific access levels to users.
 
 ```{toctree}
 :titlesonly:
@@ -29,12 +29,12 @@ API and clients <api-and-clients>
 
 ## Service orchestration
 
-Pebble can automatically start and stop services according to dependencies in your service definition.
+Pebble automatically starts and stops services if you specify dependencies between services.
 
 ```{toctree}
 :titlesonly:
 :maxdepth: 1
 
 Service dependencies <service-dependencies>
 Service start order <service-start-order>
-```
+```
diff --git a/docs/how-to/index.md b/docs/how-to/index.md
@@ -29,7 +29,7 @@ Manage service dependencies <service-dependencies>
 
 ## Identities
 
-Use named identities to allow additional users to access the API.
+Use named "identities" to allow additional users to access the API.
 
 ```{toctree}
 :titlesonly: