docs: update generated docs (#1053)

Updates for both discovery docs and epydoc API Documentation

Fixes: #1049
diff --git a/docs/epy/googleapiclient.http.MediaUpload-class.html b/docs/epy/googleapiclient.http.MediaUpload-class.html
index 8e01938..bb0ca39 100644
--- a/docs/epy/googleapiclient.http.MediaUpload-class.html
+++ b/docs/epy/googleapiclient.http.MediaUpload-class.html
@@ -57,38 +57,42 @@
 </table>
 <!-- ==================== CLASS DESCRIPTION ==================== -->
 <h1 class="epydoc">Class MediaUpload</h1><p class="nomargin-top"><span class="codelink"><a href="googleapiclient.http-pysrc.html#MediaUpload">source&nbsp;code</a></span></p>
-<center>
-
-</center>
-<hr />
-<pre class="literalblock">
-Describes a media object to upload.
-
-Base class that defines the interface of MediaUpload subclasses.
-
-Note that subclasses of MediaUpload may allow you to control the chunksize
-when uploading a media object. It is important to keep the size of the chunk
-as large as possible to keep the upload efficient. Other factors may influence
-the size of the chunk you use, particularly if you are working in an
-environment where individual HTTP requests may have a hardcoded time limit,
-such as under certain classes of requests under Google App Engine.
-
-Streams are io.Base compatible objects that support seek(). Some MediaUpload
-subclasses support using streams directly to upload data. Support for
-streaming may be indicated by a MediaUpload sub-class and if appropriate for a
-platform that stream will be used for uploading the media object. The support
-for streaming is indicated by has_stream() returning True. The stream() method
-should return an io.Base object that supports seek(). On platforms where the
-underlying httplib module supports streaming, for example Python 2.6 and
-later, the stream will be passed into the http library which will result in
-less memory being used and possibly faster uploads.
-
-If you need to upload media that can't be uploaded using any of the existing
-MediaUpload sub-class then you can sub-class MediaUpload for your particular
-needs.
-
+<pre class="base-tree">
+object --+
+         |
+        <strong class="uidshort">MediaUpload</strong>
 </pre>
 
+<dl><dt>Known Subclasses:</dt>
+<dd>
+      <ul class="subclass-list">
+<li><a href="googleapiclient.http.MediaIoBaseUpload-class.html">MediaIoBaseUpload</a></li>  </ul>
+</dd></dl>
+
+<hr />
+<p>Describes a media object to upload.</p>
+  <p>Base class that defines the interface of MediaUpload subclasses.</p>
+  <p>Note that subclasses of MediaUpload may allow you to control the 
+  chunksize when uploading a media object. It is important to keep the size
+  of the chunk as large as possible to keep the upload efficient. Other 
+  factors may influence the size of the chunk you use, particularly if you 
+  are working in an environment where individual HTTP requests may have a 
+  hardcoded time limit, such as under certain classes of requests under 
+  Google App Engine.</p>
+  <p>Streams are io.Base compatible objects that support seek(). Some 
+  MediaUpload subclasses support using streams directly to upload data. 
+  Support for streaming may be indicated by a MediaUpload sub-class and if 
+  appropriate for a platform that stream will be used for uploading the 
+  media object. The support for streaming is indicated by has_stream() 
+  returning True. The stream() method should return an io.Base object that 
+  supports seek(). On platforms where the underlying httplib module 
+  supports streaming, for example Python 2.6 and later, the stream will be 
+  passed into the http library which will result in less memory being used 
+  and possibly faster uploads.</p>
+  <p>If you need to upload media that can't be uploaded using any of the 
+  existing MediaUpload sub-class then you can sub-class MediaUpload for 
+  your particular needs.</p>
+
 <!-- ==================== INSTANCE METHODS ==================== -->
 <a name="section-InstanceMethods"></a>
 <table class="summary" border="1" cellpadding="3"
@@ -233,8 +237,8 @@
     </td><td class="summary">
       <table width="100%" cellpadding="0" cellspacing="0" border="0">
         <tr>
-          <td><span class="summary-sig"><a href="googleapiclient.http.MediaUpload-class.html#_to_json" class="summary-sig-name" onclick="show_private();">_to_json</a>(<span class="summary-sig-arg">self</span>,
-        <span class="summary-sig-arg">strip</span>=<span class="summary-sig-default">None</span>)</span><br />
+          <td><span class="summary-sig"><a href="googleapiclient.http.MediaUpload-class.html#_to_json" class="summary-sig-name" onclick="show_private();">_to_json</a>(<span class="summary-sig-arg">*args</span>,
+        <span class="summary-sig-arg">**kwargs</span>)</span><br />
       Utility function for creating a JSON representation of a MediaUpload.</td>
           <td align="right" valign="top">
             <span class="codelink"><a href="googleapiclient.http-pysrc.html#MediaUpload._to_json">source&nbsp;code</a></span>
@@ -556,8 +560,8 @@
 <tr><td>
   <table width="100%" cellpadding="0" cellspacing="0" border="0">
   <tr valign="top"><td>
-  <h3 class="epydoc"><span class="sig"><span class="sig-name">_to_json</span>(<span class="sig-arg">self</span>,
-        <span class="sig-arg">strip</span>=<span class="sig-default">None</span>)</span>
+  <h3 class="epydoc"><span class="sig"><span class="sig-name">_to_json</span>(<span class="sig-arg">*args</span>,
+        <span class="sig-arg">**kwargs</span>)</span>
   </h3>
   </td><td align="right" valign="top"
     ><span class="codelink"><a href="googleapiclient.http-pysrc.html#MediaUpload._to_json">source&nbsp;code</a></span>&nbsp;
@@ -668,7 +672,7 @@
 <table border="0" cellpadding="0" cellspacing="0" width="100%%">
   <tr>
     <td align="left" class="footer">
-    Generated by Epydoc 3.0.1 on Thu Apr 30 17:06:05 2020
+    Generated by Epydoc 3.0.1 on Fri Oct  2 20:46:22 2020
     </td>
     <td align="right" class="footer">
       <a target="mainFrame" href="http://epydoc.sourceforge.net"