docs: [LongRunning] clarity and typo fixes for documentation

LongRunning/src/LongRunning/Client/OperationsClient.php

@@ -44,12 +44,12 @@
  * Service Description: Manages long-running operations with an API service.
  *
  * When an API method normally takes long time to complete, it can be designed
- * to return [Operation][google.longrunning.Operation] to the client, and the client can use this
- * interface to receive the real response asynchronously by polling the
- * operation resource, or pass the operation resource to another API (such as
- * Google Cloud Pub/Sub API) to receive the response.  Any API service that
- * returns long-running operations should implement the `Operations` interface
- * so developers can have a consistent client experience.
+ * to return [Operation][google.longrunning.Operation] to the client, and the
+ * client can use this interface to receive the real response asynchronously by
+ * polling the operation resource, or pass the operation resource to another API
+ * (such as Pub/Sub API) to receive the response.  Any API service that returns
+ * long-running operations should implement the `Operations` interface so
+ * developers can have a consistent client experience.
  *
  * This class provides the ability to make remote calls to the backing service through method
  * calls that map to API methods.
@@ -185,8 +185,9 @@ public function __call($method, $args)
      * other methods to check whether the cancellation succeeded or whether the
      * operation completed despite cancellation. On successful cancellation,
      * the operation is not deleted; instead, it becomes an operation with
-     * an [Operation.error][google.longrunning.Operation.error] value with a [google.rpc.Status.code][google.rpc.Status.code] of 1,
-     * corresponding to `Code.CANCELLED`.
+     * an [Operation.error][google.longrunning.Operation.error] value with a
+     * [google.rpc.Status.code][google.rpc.Status.code] of `1`, corresponding to
+     * `Code.CANCELLED`.
      *
      * The async variant is {@see OperationsClient::cancelOperationAsync()} .
      *
@@ -268,14 +269,6 @@ public function getOperation(GetOperationRequest $request, array $callOptions =
      * Lists operations that match the specified filter in the request. If the
      * server doesn't support this method, it returns `UNIMPLEMENTED`.
      *
-     * NOTE: the `name` binding allows API services to override the binding
-     * to use different resource name schemes, such as `users/*/operations`. To
-     * override the binding, API services can add a binding such as
-     * `"/v1/{name=users/*}/operations"` to their service configuration.
-     * For backwards compatibility, the default name includes the operations
-     * collection id, however overriding users must ensure the name binding
-     * is the parent resource, without the operations collection id.
-     *
      * The async variant is {@see OperationsClient::listOperationsAsync()} .
      *
      * @example samples/OperationsClient/list_operations.php

LongRunning/src/LongRunning/Gapic/OperationsGapicClient.php

@@ -46,12 +46,12 @@
  * Service Description: Manages long-running operations with an API service.
  *
  * When an API method normally takes long time to complete, it can be designed
- * to return [Operation][google.longrunning.Operation] to the client, and the client can use this
- * interface to receive the real response asynchronously by polling the
- * operation resource, or pass the operation resource to another API (such as
- * Google Cloud Pub/Sub API) to receive the response.  Any API service that
- * returns long-running operations should implement the `Operations` interface
- * so developers can have a consistent client experience.
+ * to return [Operation][google.longrunning.Operation] to the client, and the
+ * client can use this interface to receive the real response asynchronously by
+ * polling the operation resource, or pass the operation resource to another API
+ * (such as Pub/Sub API) to receive the response.  Any API service that returns
+ * long-running operations should implement the `Operations` interface so
+ * developers can have a consistent client experience.
  *
  * This class provides the ability to make remote calls to the backing service through method
  * calls that map to API methods. Sample code to get started:
@@ -188,8 +188,9 @@ public function __construct(array $options = [])
      * other methods to check whether the cancellation succeeded or whether the
      * operation completed despite cancellation. On successful cancellation,
      * the operation is not deleted; instead, it becomes an operation with
-     * an [Operation.error][google.longrunning.Operation.error] value with a [google.rpc.Status.code][google.rpc.Status.code] of 1,
-     * corresponding to `Code.CANCELLED`.
+     * an [Operation.error][google.longrunning.Operation.error] value with a
+     * [google.rpc.Status.code][google.rpc.Status.code] of `1`, corresponding to
+     * `Code.CANCELLED`.
      *
      * Sample code:
      * ```
@@ -337,14 +338,6 @@ public function getOperation($name, array $optionalArgs = [])
      * Lists operations that match the specified filter in the request. If the
      * server doesn't support this method, it returns `UNIMPLEMENTED`.
      *
-     * NOTE: the `name` binding allows API services to override the binding
-     * to use different resource name schemes, such as `users/*/operations`. To
-     * override the binding, API services can add a binding such as
-     * `"/v1/{name=users/*}/operations"` to their service configuration.
-     * For backwards compatibility, the default name includes the operations
-     * collection id, however overriding users must ensure the name binding
-     * is the parent resource, without the operations collection id.
-     *
      * Sample code:
      * ```
      * $operationsClient = new OperationsClient();