Browse Source

fix typo mistakes

Change-Id: I90b17fd6b15a3a971614486782fec88acc0b6304
master
MaoyangLiu 5 months ago
parent
commit
6088e871c1

+ 2
- 2
specs/stein/backlog/swift-extended-cluster-operations.rst View File

@@ -42,7 +42,7 @@ effectively maintain a Swift cluster over time:
42 42
   have already been initialised.
43 43
 
44 44
 This forces operators to manually apply changes like adjusting the
45
-partition-power to accomodate for additional storage added to the cluster. This
45
+partition-power to accommodate for additional storage added to the cluster. This
46 46
 poses great risk since manually editing the rings/builders and syncing them
47 47
 across the cluster could easily conflict with the swift-proxy charm's native
48 48
 support for doing this resulting in a broken cluster.
@@ -64,7 +64,7 @@ refuse to make changes until the operator has paused the swift-proxy units i.e.
64 64
 placed them into "maintenance mode" which will shutdown the api services and
65 65
 block any restarts until the units are resumed. The user will also have the
66 66
 option to set disable-ring-balance=true if they want check that their changes
67
-have been applied successully (to the builder files) prior to having the rings
67
+have been applied successfully (to the builder files) prior to having the rings
68 68
 rebuilt and sycned across the cluster.
69 69
 
70 70
 For the swift-storage charms, where currently one can only add devices but not

+ 1
- 1
specs/stein/implemented/octavia.rst View File

@@ -49,7 +49,7 @@ software itself and dynamic scaling of the service.
49 49
 
50 50
 On the scaling side, most if not all, of the ``octavia`` services benefit from
51 51
 being scaled out proportional to the number of running load balancers and load
52
-balancer life cycle events.  Thus it makse sense to co-locate the API, Worker,
52
+balancer life cycle events.  Thus it makes sense to co-locate the API, Worker,
53 53
 Health Manager and Housekeeping Manager daemons in the same charm unit, and
54 54
 scale by increasing the number of charm units deployed.
55 55
 

Loading…
Cancel
Save