Skip to content

Commit 1312ab2

Browse files
committed
fix typos
1 parent 008a289 commit 1312ab2

File tree

1 file changed

+9
-8
lines changed

1 file changed

+9
-8
lines changed

content/06.quality_criteria.md

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -254,15 +254,15 @@ of their data.
254254
* **[SvcQC.Pol01.1]** Acceptable Usage Policy (AUP): Is a set of rules applied
255255
by the owner, creator or administrator of a network, website, or service, that
256256
restrict the ways in which the network, website or system may be used and sets
257-
guidelines as to how it should be used. The AUP can also be referred as: Acceptable
257+
guidelines as to how it should be used. The AUP can also be referred to as: Acceptable
258258
Use Policy or Fair Use Policy.
259259
* **[SvcQC.Pol01.2]** Access Policy or Terms of Use: represent a binding legal
260260
contract between the users (and/or customers), and the Provider of the **Service**.
261261
The Access Policy mandates the users (and/or customers) access to and the use of
262262
the Provider’s **Service**.
263263
* **[SvcQC.Pol01.3]** Privacy Policy: Data privacy statement informing the users
264-
(and/or costumers), about which personal data is collected and processed when they
265-
use and interact with the **Service**. It states which rights the users (and/or costumers)
264+
(and/or customers), about which personal data is collected and processed when they
265+
use and interact with the **Service**. It states which rights the users (and/or customers)
266266
have regarding the processing of their data.
267267

268268
### Support [SvcQC.Sup]
@@ -290,7 +290,7 @@ Agreement (SLA) with user communities.
290290
Monitoring is a periodic testing of the **Service**. It requires a monitoring
291291
service from where tests are executed or sent and results of those tests are shown.
292292
The tests can be the same, in part or in total of the Functional tests.
293-
The technology used for the monitoring, is left to the developers of the underlying
293+
The technology used for the monitoring is left to the developers of the underlying
294294
software to decide eventually with input from the infrastructure(s),
295295
where the **Service** is foreseen to be integrated.
296296

@@ -319,13 +319,13 @@ where the **Service** is foreseen to be integrated.
319319

320320
The automated deployment of **Services** implies the use of code to install and
321321
configure them in the target infrastructures. Infrastructure as Code (IaC)
322-
templates allow operations team to treat service provisioning and deployment in
322+
templates allow operations teams to treat service provisioning and deployment in
323323
a similar fashion as developers manage the software code.
324324

325325
Consequently, IaC enables the paradigm of immutable infrastructure deployment
326326
and maintenance, where **Services** are never updated, but deprovisioned and
327327
redeployed. An immutable infrastructure simplifies maintenance and enhances
328-
repeteability and reliability.
328+
repeatability and reliability.
329329

330330
* **[SvcQC.Aud01]** A production-ready **Service** SHOULD be deployed as a
331331
workable system with the minimal user or system administrator interaction
@@ -349,8 +349,9 @@ of users registered in the **Service**, or using it actively. Also
349349
accounting is important to track resource usage per user or group
350350
of users, either or both computing and storage resources.
351351

352-
Although the the metrics maybe published in external services, this
353-
is a common case in federated infrastructures such as EOSC.
352+
Although the metrics may be published in external services managed
353+
by the infrastructure, this is a common case in federated
354+
infrastructures such as EOSC.
354355

355356
* **[SvcQC.Met01]** The **Service** SHOULD implement the collection
356357
of metrics.

0 commit comments

Comments
 (0)