fix linter errors

aep-dev · Oct 13, 2023 · 35446e5 · 35446e5
1 parent d028909
commit 35446e5
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 7 deletions.
diff --git a/aep/general/0002/aep.md b/aep/general/0002/aep.md
@@ -6,8 +6,8 @@ AEP provides a numbering system that:
 
 - Groups AEPs primarily by their purpose, and secondarily by the general theme
   they are discussing.
-- Allows for new AEPs to be added incrementally, without adjusting the
-  numbers of existing AEPs.
+- Allows for new AEPs to be added incrementally, without adjusting the numbers
+  of existing AEPs.
 
 ## AEP Blocks
 
@@ -17,7 +17,7 @@ The list of blocks are:
 | --------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | 1-999     | meta topics     | topics that are not directly related to API guidance, but provide guidance or clarity for the AEPs themselves                                                                         |
 | 1000-1999 | specification   | APIs which are AEP-compliant **must** adhere to these AEPs. Clients authors may read these AEPs to determine what behavior they can rely on when integrating with AEP-compliant APIs. |
-| 2000-2999 | design patterns | Best practice design patterns for common API use cases. API authors should read these AEPs to help with the  design of their APIs.                                                    |
+| 2000-2999 | design patterns | Best practice design patterns for common API use cases. API authors should read these AEPs to help with the design of their APIs.                                                     |
 | 3000-9999 | reserved        | Reserved for future use by the AEP project.                                                                                                                                           |
 
 ## Organization-specific AEPs
@@ -36,4 +36,4 @@ Similar to [google.aip.dev](google.aip.dev), the organizations supporting the
 AEP project found the need for providing organization-specific guidance that is
 a superset of the open specification. By allocating a specific range,
 organizations may safely extend the AEPs without concern of conflicting AEP
-numbers.
+numbers.
diff --git a/aep/general/0151/lro.oas.yaml b/aep/general/0151/lro.oas.yaml
@@ -22,12 +22,15 @@ components:
       properties:
         name:
           type: string
-          description: The server-assigned name, which is only unique within the same service that originally returns it.
+          description:
+            The server-assigned name, which is only unique within the same
+            service that originally returns it.
         done:
           type: boolean
           description: >-
-            If the value is false, it means the operation is still in progress. If true, the operation is completed,
-            and either response or error is available.
+            If the value is false, it means the operation is still in progress.
+            If true, the operation is completed, and either response or error
+            is available.
         error:
           $ref: '#/components/schemas/Error'
       required: