Browse Source

spelling error

fixing the double-quote chars in the RST source to be regular double-quotes

Change-Id: Iaeb652d63d093091af9f321e421fd082948c5614
melissaml 1 year ago
parent
commit
6b6424f392

+ 16
- 16
specs/kilo/artifact-repository.rst View File

@@ -217,7 +217,7 @@ at any time - their value is set automatically by the repository.
217 217
      - Immutable
218 218
      - Yes
219 219
      - String following the SemVer notation
220
-     - Defines the version of the artifact. See “Artifact versioning” section
220
+     - Defines the version of the artifact. See "Artifact versioning" section
221 221
        below for the details.
222 222
    * - Description
223 223
      - Mutable
@@ -241,7 +241,7 @@ at any time - their value is set automatically by the repository.
241 241
      - N/A
242 242
      - Enum, any of: CREATING, ACTIVE, DEACTIVATED, DELETED
243 243
      - A system field set by the repository, indicating the current phase of
244
-       the artifact's lifecycle. See “Artifact Lifecyle” below for details
244
+       the artifact's lifecycle. See "Artifact Lifecyle" below for details
245 245
    * - Owner
246 246
      - System
247 247
      - N/A
@@ -291,13 +291,13 @@ the following properties:
291 291
   The following types are supported:
292 292
 
293 293
   * *String* - simple string value (255 characters max). In listing queries
294
-    may use this field to filter artifacts by value equality (e.g. filter all
294
+    may use this field to filter artifacts by value equality (e.g. "filter all
295 295
     the artifacts of type ‘Image’ having the field ‘OS_TYPE’ equal to
296
-    ‘Linux’)
296
+    ‘Linux’")
297 297
   * *Integer*. - integer field. In listing queries may use this field to
298
-    filter artifacts by both value equality and value range (e.g. filter all
298
+    filter artifacts by both value equality and value range (e.g. "filter all
299 299
     the artifacts of type ‘Image’ having the field ‘REQUIRED_RAM’ less or equal
300
-    to 16)
300
+    to 16")
301 301
   * *Numeric* - same as Integer, but stored as Numeric
302 302
   * *Boolean** - boolean values, having either 'True' or 'False' as the value.
303 303
     In listing queries may use this field to filter artifacts by value equality.
@@ -383,8 +383,8 @@ images are stored independently from their definitions in the current version
383 383
 of Glance.
384 384
 
385 385
 When the artifact is initially created in the repository (the record is
386
-inserted into the database), it is in the CREATING state (see the Artifact
387
-Lifecycle section below) and has no binary data associated. Then - before
386
+inserted into the database), it is in the CREATING state (see the "Artifact
387
+Lifecycle" section below) and has no binary data associated. Then - before
388 388
 publishing the artifact - its owner may upload the data by using the
389 389
 appropriate API calls or specify the location/uri of the existing binary blob
390 390
 pre-uploaded to some back-end storage.
@@ -412,8 +412,8 @@ binary object associated.
412 412
 
413 413
 This means that each artifact may have a number of different BLOBs associated.
414 414
 
415
-The amount of blobs and their types (“Heat template”, "Provider Templates" and
416
-“Icon” in the example above) are defined per each artifact type. When the
415
+The amount of blobs and their types ("Heat template", "Provider Templates" and
416
+"Icon" in the example above) are defined per each artifact type. When the
417 417
 artifact is in CREATING state its owner will have to upload all the required
418 418
 parts one-by-one, specifying their types every time. If some required blob is
419 419
 not uploaded, the "publishing check" will not pass and the artifact will not be
@@ -441,9 +441,9 @@ properties:
441 441
   If set to None, then the number of blobs in BLOBs list per
442 442
   artifact has no upper bound.
443 443
 
444
-  *For example, the above-mentioned artifact type “Heat template” may define
445
-  an optional BinaryObjectList property with the Name set to “ProviderTemplate”,
446
-  and a required BinaryObjectList property with the name “Icon” and minimum
444
+  *For example, the above-mentioned artifact type "Heat template" may define
445
+  an optional BinaryObjectList property with the Name set to "ProviderTemplate",
446
+  and a required BinaryObjectList property with the name "Icon" and minimum
447 447
   and maximum length constraints equal to 1.
448 448
   This means that the artifacts of this type have to contain exactly one icon
449 449
   blob and zero or more provider template blobs.*
@@ -452,7 +452,7 @@ The repository provides an API call to inspect the blob contents of each
452 452
 artifact.
453 453
 
454 454
   *In the example above the API returns a dictionary containing two
455
-  keys: “ProviderTemplates” and “Icon”. The first key defined a list of
455
+  keys: "ProviderTemplates" and "Icon". The first key defined a list of
456 456
   records, each one corresponding to a different blob with a provider template,
457 457
   the second one defines a single record corresponding to the blob with the
458 458
   icon. Each of the blob records contains an id of the particular blob, which
@@ -499,8 +499,8 @@ editing.
499 499
 
500 500
 The dependencies cannot be circular (e.g if A depends on B, B depends on C and
501 501
 C depends on D, then D cannot depend on A), and the published artifact may not
502
-depend on an artifact being in a “CREATING” state. For example, if A depends
503
-on B and both are in “CREATING” state, then B should be published before A,
502
+depend on an artifact being in a "CREATING" state. For example, if A depends
503
+on B and both are in "CREATING" state, then B should be published before A,
504 504
 otherwise the publishing check of A will fail.
505 505
 
506 506
 The dependencies may be created only on the artifacts which belong to the same

+ 1
- 1
specs/newton/approved/glance/glare-api.rst View File

@@ -185,7 +185,7 @@ glossary and list of Use Cases.
185 185
 * *Artifact Blob* - property type that defines binary data for Artifact.
186 186
   User can download Artifact blob from Glare. Each blob property has a flag
187 187
   *external*, that indicates if the property was created during file upload
188
-  (False) or by direct user request (True). In other words, “external” means
188
+  (False) or by direct user request (True). In other words, "external" means
189 189
   that blob property url is just a reference to some external file and Glare
190 190
   does not manage the blob operations in that case.
191 191
   Json schema that defines blob format:

+ 1
- 1
specs/newton/approved/python-glanceclient/lite-specs.rst View File

@@ -25,7 +25,7 @@ Optionals (please remove this line and fill or remove the rest until End of Temp
25 25
 :timeline: <Estimation of the time needed to complete the work.>
26 26
 
27 27
 :link: <Link to the change in gerrit that already would provide the `solution`.
28
-       After commiting the Spec Lite depend the change to the Spec Lite commit.>
28
+       After committing the Spec Lite depend the change to the Spec Lite commit.>
29 29
 
30 30
 :reviewers: <If reviewers has been agreed for the functionality, list them here.>
31 31
 

+ 2
- 2
specs/ocata/approved/glance/rolling-upgrades.rst View File

@@ -63,8 +63,8 @@ listed in [GOV1]_.  They are:
63 63
         This plan should clearly call out the supported configuration(s) that
64 64
         are expected to work, unless there are no such caveats. This does not
65 65
         require complete elimination of downtime during upgrades, but rather
66
-        reducing the scope from “all services” to “some services at a time.” In
67
-        other words, “restarting all API services together” is a reasonable
66
+        reducing the scope from "all services" to "some services at a time." In
67
+        other words, "restarting all API services together" is a reasonable
68 68
         restriction.
69 69
 
70 70
     The Glance services consist of the Glance API server and the optional

+ 1
- 1
specs/ocata/approved/glance_store/lite-specs.rst View File

@@ -25,7 +25,7 @@ Optionals (please remove this line and fill or remove the rest until End of Temp
25 25
 :timeline: <Estimation of the time needed to complete the work.>
26 26
 
27 27
 :link: <Link to the change in gerrit that already would provide the `solution`.
28
-       After commiting the Spec Lite depend the change to the Spec Lite commit.>
28
+       After committing the Spec Lite depend the change to the Spec Lite commit.>
29 29
 
30 30
 :reviewers: <If reviewers has been agreed for the functionality, list them here.>
31 31
 

+ 1
- 1
specs/ocata/approved/python-glanceclient/lite-specs.rst View File

@@ -25,7 +25,7 @@ Optionals (please remove this line and fill or remove the rest until End of Temp
25 25
 :timeline: <Estimation of the time needed to complete the work.>
26 26
 
27 27
 :link: <Link to the change in gerrit that already would provide the `solution`.
28
-       After commiting the Spec Lite depend the change to the Spec Lite commit.>
28
+       After committing the Spec Lite depend the change to the Spec Lite commit.>
29 29
 
30 30
 :reviewers: <If reviewers has been agreed for the functionality, list them here.>
31 31
 

+ 1
- 1
specs/pike/approved/glance/lite-specs.rst View File

@@ -25,7 +25,7 @@ Optionals (please remove this line and fill or remove the rest until End of Temp
25 25
 :timeline: <Estimation of the time needed to complete the work.>
26 26
 
27 27
 :link: <Link to the change in gerrit that already would provide the `solution`.
28
-       After commiting the Spec Lite depend the change to the Spec Lite commit.>
28
+       After committing the Spec Lite depend the change to the Spec Lite commit.>
29 29
 
30 30
 :reviewers: <If reviewers has been agreed for the functionality, list them here.>
31 31
 

+ 1
- 1
specs/pike/approved/glance_store/lite-specs.rst View File

@@ -25,7 +25,7 @@ Optionals (please remove this line and fill or remove the rest until End of Temp
25 25
 :timeline: <Estimation of the time needed to complete the work.>
26 26
 
27 27
 :link: <Link to the change in gerrit that already would provide the `solution`.
28
-       After commiting the Spec Lite depend the change to the Spec Lite commit.>
28
+       After committing the Spec Lite depend the change to the Spec Lite commit.>
29 29
 
30 30
 :reviewers: <If reviewers has been agreed for the functionality, list them here.>
31 31
 

+ 1
- 1
specs/pike/approved/python-glanceclient/lite-specs.rst View File

@@ -25,7 +25,7 @@ Optionals (please remove this line and fill or remove the rest until End of Temp
25 25
 :timeline: <Estimation of the time needed to complete the work.>
26 26
 
27 27
 :link: <Link to the change in gerrit that already would provide the `solution`.
28
-       After commiting the Spec Lite depend the change to the Spec Lite commit.>
28
+       After committing the Spec Lite depend the change to the Spec Lite commit.>
29 29
 
30 30
 :reviewers: <If reviewers has been agreed for the functionality, list them here.>
31 31
 

+ 1
- 1
specs/spec-lite-template.rst View File

@@ -33,7 +33,7 @@ Spec Lite: <Your Title Here>
33 33
 :timeline: <List the milestone by which you expect this work to be completed.>
34 34
 
35 35
 :link: <Link to the change in gerrit that already would provide the `solution`.
36
-       After commiting the Spec Lite depend the change to the Spec Lite commit.>
36
+       After committing the Spec Lite depend the change to the Spec Lite commit.>
37 37
 
38 38
 :reviewers: <If specific reviewers have agreed to champion this proposal, list
39 39
             them here.>

Loading…
Cancel
Save