style: apply suggestions from code review

Thanks, Tony! Co-authored-by: Tony Meyer <[email protected]>
canonical · Feb 12, 2025 · 2042d05 · 2042d05
1 parent 3c58a69
commit 2042d05
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/docs/howto/write-unit-tests-for-a-charm.md b/docs/howto/write-unit-tests-for-a-charm.md
@@ -99,7 +99,7 @@ harness.charm.unit.status = BlockedStatus("Testing")
 Any of your charm’s properties and methods (including event callbacks) can be accessed using
 `harness.charm`.  You can check out the [harness API
 docs](ops_testing_harness) for more ways to use the
-harness to trigger other events and to test your charm (e.g. triggering leadership related events,
+harness to trigger other events and to test your charm (e.g. triggering events regarding leadership,
 testing pebble events and sidecar container interactions, etc.).
 
 

diff --git a/ops/charm.py b/ops/charm.py
@@ -682,7 +682,7 @@ class RelationBrokenEvent(RelationEvent):
 
 
 class StorageEvent(HookEvent):
-    """Base class representing storage related events.
+    """Base class representing events to do with storage.
 
     Juju can provide a variety of storage types to a charms. The
     charms can define several different types of storage that are

diff --git a/testing/src/scenario/state.py b/testing/src/scenario/state.py
@@ -490,7 +490,7 @@ def _next_relation_id(*, update: bool = True):
 
 @dataclasses.dataclass(frozen=True)
 class RelationBase(_max_posargs(2)):
-    """Base class for the various types of relation (integration)."""
+    """Base class for the various types of relation."""
 
     endpoint: str
     """Relation endpoint name. Must match some endpoint name defined in the metadata."""